Executive summary
edgarfgp/Fabulous.AST falls short of our standard for production because we found no recorded design decisions and no architecture document or diagram. It scores 61 out of 100 and is rated Adequate, and all 17 of its critical findings are security problems in the build pipeline.
Maturity, at 55, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 6 points. Adding test instructions to the README is another step, worth about 3 points. Raising Maturity to 70 would lift the score to about 65.
Fifteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two secrets can leak from the build pipeline. Pinning each tool to an exact version and limiting each secret to its own step would close both risks.
The product code is 23,846 lines, about €42,000 to rebuild.
If Maturity rose from 55 to 70, the lowest score rated Strong, the score would rise from 61 to about 65.
New since the last survey: 24 findings
- Code Duplication · Edited copies of one member (3 members, 135+ corresponding lines) src/Fabulous.AST/Widgets/Expressions/DotIndexedSet.fs
- Code Duplication · Edited copy of a member (68 corresponding lines) src/Fabulous.AST/Widgets/Expressions/Lambda.fs
- Code Duplication · Edited copy of a member (57 corresponding lines) src/Fabulous.AST/Widgets/Patterns/As.fs
- Code Duplication · Edited copy of a member (59 corresponding lines) src/Fabulous.AST/Widgets/Expressions/TryFinally.fs
- Code Duplication · Edited copy of a member (86 corresponding lines) src/Fabulous.AST/Widgets/TypeDefinitions/Augment.fs
- Code Duplication · Edited copy of a member (38 corresponding lines) src/Fabulous.AST/Widgets/Expressions/IndexWithoutDot.fs
- Code Duplication · Edited copy of a member (37 corresponding lines) src/Fabulous.AST/Widgets/Expressions/LongIdentSet.fs
- Code Duplication · Edited copy of a member (34 corresponding lines) src/Fabulous.AST/Widgets/Expressions/StructTuple.fs
- Code Duplication · Edited copy of a member (35 corresponding lines) src/Fabulous.AST/Widgets/Patterns/Named.fs
- Code Duplication · Edited copies of one member (3 members, 28+ corresponding lines) src/Fabulous.AST/Widgets/Patterns/Ands.fs
- Code Duplication · Edited copies of one member (3 members, 24+ corresponding lines) src/Fabulous.AST/Widgets/Expressions/Paren.fs
- Code Duplication · Edited copies of one member (4 members, 19+ corresponding lines) src/Fabulous.AST/Widgets/Expressions/Ident.fs
- Code Coverage · Low coverage: src/Fabulous.AST/Widgets/MemberDefinitions/MemberDefn.fs src/Fabulous.AST/Widgets/MemberDefinitions/MemberDefn.fs
- Code Coverage · Low coverage: src/Fabulous.AST/Widgets/ModuleDeclarations/ModuleDecl.fs src/Fabulous.AST/Widgets/ModuleDeclarations/ModuleDecl.fs
- Code Coverage · Low coverage: src/Fabulous.AST/Rewrite/Rewrite.fs src/Fabulous.AST/Rewrite/Rewrite.fs
- Code Coverage · Low coverage: src/Fabulous.AST/Widgets/Types/WithSubTypeConstraint.fs src/Fabulous.AST/Widgets/Types/WithSubTypeConstraint.fs
- Code Coverage · Low coverage: src/Fabulous.AST/Widgets/Types/LongIdentApp.fs src/Fabulous.AST/Widgets/Types/LongIdentApp.fs
- Code Coverage · Low coverage: src/Fabulous.AST/Widgets/Expressions/ComputationExpressionStatement.fs src/Fabulous.AST/Widgets/Expressions/ComputationExpressionStatement.fs
- Code Coverage · Low coverage: src/Fabulous.AST/Widgets/Expressions/JoinIn.fs src/Fabulous.AST/Widgets/Expressions/JoinIn.fs
- Code Coverage · Low coverage: src/Fabulous.AST/Widgets/Expressions/Typar.fs src/Fabulous.AST/Widgets/Expressions/Typar.fs
- Code Coverage · Low coverage: src/Fabulous.AST/Widgets/Expressions/TraitCall.fs src/Fabulous.AST/Widgets/Expressions/TraitCall.fs
- Code Coverage · Low coverage: src/Fabulous.AST/DSL/Primitives.fs src/Fabulous.AST/DSL/Primitives.fs
- Code Coverage · Low coverage: src/Fabulous.AST/DSL/Array.fs src/Fabulous.AST/DSL/Array.fs
- Code Coverage · No test project references Fabulous.AST.Build extensions/Fabulous.AST.Build/Fabulous.AST.Build.fsproj
Fixed since the last survey: 1 finding
- Documentation (README) · README may be stale
Rebuild cost: about €42,000 · Estimate
| Cost to rebuild | €14,000 to €70,000, for 233 to 740 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 61. 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: 23,846 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 — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 WidgetAttributeDefinitions | 2 WidgetCollectionAttributeDefinitions | 3 Fabulous.AST | 4 ExceptionDefn | 5 ScalarAttributeDefinitions | 6 AbstractSlot | 7 AnonStructRecord | 8 App | 9 AppLongIdentAndSingleParenArg | 10 AppWithLambda | 11 As | 12 AttributeNode | 13 Attributes | 14 Augmentation | 15 AutoPropertyMember | 16 BindingNode | 17 ChainLink | 18 ComputationExpressionStatement | 19 Delegate | 20 DotNamedIndexedPropertySet | 21 Enum | 22 EnumCase | 23 ExplicitConstructorMember | 24 ExternBinding | 25 ExternBindingPattern | 26 Field | 27 FillExprNode | 28 For | 29 ImplicitConstructor | 30 MemberDefn | 31 ModuleDecl | 32 ModuleOrNamespace | 33 ObjExpr | 34 Pattern | 35 PropertyGetSetBinding | 36 TypeDefn | 37 TypeDefnExplicit | 38 TypeDefnRegular | 39 Val | 40 Widgets |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 WidgetAttributeDefinitions | 2 | |||||||||||||||||||||||||||||||||||||||
| 2 WidgetCollectionAttributeDefinitions | 1 | |||||||||||||||||||||||||||||||||||||||
| 3 Fabulous.AST | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 4 ExceptionDefn | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 5 ScalarAttributeDefinitions | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 AbstractSlot | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 7 AnonStructRecord | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 8 App | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 AppLongIdentAndSingleParenArg | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 10 AppWithLambda | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 As | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 AttributeNode | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 Attributes | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 14 Augmentation | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 AutoPropertyMember | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 BindingNode | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 17 ChainLink | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 ComputationExpressionStatement | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 Delegate | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 DotNamedIndexedPropertySet | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 Enum | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 EnumCase | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 ExplicitConstructorMember | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 ExternBinding | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 ExternBindingPattern | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 Field | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 FillExprNode | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 For | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 ImplicitConstructor | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 MemberDefn | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 ModuleDecl | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 ModuleOrNamespace | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 33 ObjExpr | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 Pattern | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 PropertyGetSetBinding | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 TypeDefn | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 TypeDefnExplicit | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 TypeDefnRegular | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 Val | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 Widgets | 1 | 1 | 2 | 1 |
1→3 WidgetAttributeDefinitions uses Fabulous.AST part of a loop✕
- Connections
- 2 pairs of types, where a type in WidgetAttributeDefinitions uses a type in Fabulous.AST.
- The types involved
Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition→Fabulous.AST.WidgetFabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition→Fabulous.AST.WidgetAttribute
- Direction
- WidgetAttributeDefinitions uses Fabulous.AST, so a change to Fabulous.AST can break WidgetAttributeDefinitions, while a change to WidgetAttributeDefinitions can't break Fabulous.AST.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
2→3 WidgetCollectionAttributeDefinitions uses Fabulous.AST part of a loop✕
- Connections
- 1 pair of types, where a type in WidgetCollectionAttributeDefinitions uses a type in Fabulous.AST.
- The types involved
Fabulous.AST.WidgetCollectionAttributeDefinitions.WidgetCollectionAttributeDefinition→Fabulous.AST.WidgetCollectionAttribute
- Direction
- WidgetCollectionAttributeDefinitions uses Fabulous.AST, so a change to Fabulous.AST can break WidgetCollectionAttributeDefinitions, while a change to WidgetCollectionAttributeDefinitions can't break Fabulous.AST.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→1 Fabulous.AST uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in Fabulous.AST uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.SingleChildBuilder`2→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- Fabulous.AST uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break Fabulous.AST, while a change to Fabulous.AST can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: Fabulous.AST uses a module listed above it, which is the healthy direction.
3→2 Fabulous.AST uses WidgetCollectionAttributeDefinitions✕
- Connections
- 2 pairs of types, where a type in Fabulous.AST uses a type in WidgetCollectionAttributeDefinitions.
- The types involved
Fabulous.AST.AttributeCollectionBuilder`2→Fabulous.AST.WidgetCollectionAttributeDefinitions.WidgetCollectionAttributeDefinitionFabulous.AST.CollectionBuilder`2→Fabulous.AST.WidgetCollectionAttributeDefinitions.WidgetCollectionAttributeDefinition
- Direction
- Fabulous.AST uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break Fabulous.AST, while a change to Fabulous.AST can't break WidgetCollectionAttributeDefinitions.
- Position
- Below the diagonal: Fabulous.AST uses a module listed above it, which is the healthy direction.
4→1 ExceptionDefn uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in ExceptionDefn uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.ExceptionDefn.ExceptionDefn→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- ExceptionDefn uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break ExceptionDefn, while a change to ExceptionDefn can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: ExceptionDefn uses a module listed above it, which is the healthy direction.
4→2 ExceptionDefn uses WidgetCollectionAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in ExceptionDefn uses a type in WidgetCollectionAttributeDefinitions.
- The types involved
Fabulous.AST.ExceptionDefn.ExceptionDefn→Fabulous.AST.WidgetCollectionAttributeDefinitions.WidgetCollectionAttributeDefinition
- Direction
- ExceptionDefn uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break ExceptionDefn, while a change to ExceptionDefn can't break WidgetCollectionAttributeDefinitions.
- Position
- Below the diagonal: ExceptionDefn uses a module listed above it, which is the healthy direction.
5→3 ScalarAttributeDefinitions uses Fabulous.AST✕
- Connections
- 1 pair of types, where a type in ScalarAttributeDefinitions uses a type in Fabulous.AST.
- The types involved
Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1→Fabulous.AST.ScalarAttribute
- Direction
- ScalarAttributeDefinitions uses Fabulous.AST, so a change to Fabulous.AST can break ScalarAttributeDefinitions, while a change to ScalarAttributeDefinitions can't break Fabulous.AST.
- Position
- Below the diagonal: ScalarAttributeDefinitions uses a module listed above it, which is the healthy direction.
6→1 AbstractSlot uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in AbstractSlot uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.AbstractSlot.AbstractSlot→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- AbstractSlot uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break AbstractSlot, while a change to AbstractSlot can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: AbstractSlot uses a module listed above it, which is the healthy direction.
6→3 AbstractSlot uses Fabulous.AST✕
- Connections
- 1 pair of types, where a type in AbstractSlot uses a type in Fabulous.AST.
- The types involved
Fabulous.AST.AbstractSlot.AbstractSlot→Fabulous.AST.MethodParamsType
- Direction
- AbstractSlot uses Fabulous.AST, so a change to Fabulous.AST can break AbstractSlot, while a change to AbstractSlot can't break Fabulous.AST.
- Position
- Below the diagonal: AbstractSlot uses a module listed above it, which is the healthy direction.
6→5 AbstractSlot uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in AbstractSlot uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.AbstractSlot.AbstractSlot→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- AbstractSlot uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break AbstractSlot, while a change to AbstractSlot can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: AbstractSlot uses a module listed above it, which is the healthy direction.
7→1 AnonStructRecord uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in AnonStructRecord uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.AnonStructRecord.AnonStructRecord→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- AnonStructRecord uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break AnonStructRecord, while a change to AnonStructRecord can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: AnonStructRecord uses a module listed above it, which is the healthy direction.
7→5 AnonStructRecord uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in AnonStructRecord uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.AnonStructRecord.AnonStructRecord→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- AnonStructRecord uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break AnonStructRecord, while a change to AnonStructRecord can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: AnonStructRecord uses a module listed above it, which is the healthy direction.
8→1 App uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in App uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.App.App→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- App uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break App, while a change to App can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: App uses a module listed above it, which is the healthy direction.
8→5 App uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in App uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.App.App→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- App uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break App, while a change to App can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: App uses a module listed above it, which is the healthy direction.
9→1 AppLongIdentAndSingleParenArg uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in AppLongIdentAndSingleParenArg uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.AppLongIdentAndSingleParenArg.AppLongIdentAndSingleParenArg→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- AppLongIdentAndSingleParenArg uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break AppLongIdentAndSingleParenArg, while a change to AppLongIdentAndSingleParenArg can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: AppLongIdentAndSingleParenArg uses a module listed above it, which is the healthy direction.
9→5 AppLongIdentAndSingleParenArg uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in AppLongIdentAndSingleParenArg uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.AppLongIdentAndSingleParenArg.AppLongIdentAndSingleParenArg→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- AppLongIdentAndSingleParenArg uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break AppLongIdentAndSingleParenArg, while a change to AppLongIdentAndSingleParenArg can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: AppLongIdentAndSingleParenArg uses a module listed above it, which is the healthy direction.
10→1 AppWithLambda uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in AppWithLambda uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.AppWithLambda.AppWithLambda→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- AppWithLambda uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break AppWithLambda, while a change to AppWithLambda can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: AppWithLambda uses a module listed above it, which is the healthy direction.
10→5 AppWithLambda uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in AppWithLambda uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.AppWithLambda.AppWithLambda→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- AppWithLambda uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break AppWithLambda, while a change to AppWithLambda can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: AppWithLambda uses a module listed above it, which is the healthy direction.
11→1 As uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in As uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.As.As→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- As uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break As, while a change to As can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: As uses a module listed above it, which is the healthy direction.
11→5 As uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in As uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.As.As→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- As uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break As, while a change to As can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: As uses a module listed above it, which is the healthy direction.
12→1 AttributeNode uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in AttributeNode uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.AttributeNode.AttributeNode→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- AttributeNode uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break AttributeNode, while a change to AttributeNode can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: AttributeNode uses a module listed above it, which is the healthy direction.
12→5 AttributeNode uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in AttributeNode uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.AttributeNode.AttributeNode→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- AttributeNode uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break AttributeNode, while a change to AttributeNode can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: AttributeNode uses a module listed above it, which is the healthy direction.
13→1 Attributes uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in Attributes uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.Attributes.Attributes→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- Attributes uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break Attributes, while a change to Attributes can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: Attributes uses a module listed above it, which is the healthy direction.
13→2 Attributes uses WidgetCollectionAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in Attributes uses a type in WidgetCollectionAttributeDefinitions.
- The types involved
Fabulous.AST.Attributes.Attributes→Fabulous.AST.WidgetCollectionAttributeDefinitions.WidgetCollectionAttributeDefinition
- Direction
- Attributes uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break Attributes, while a change to Attributes can't break WidgetCollectionAttributeDefinitions.
- Position
- Below the diagonal: Attributes uses a module listed above it, which is the healthy direction.
13→5 Attributes uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in Attributes uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.Attributes.Attributes→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- Attributes uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Attributes, while a change to Attributes can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: Attributes uses a module listed above it, which is the healthy direction.
14→2 Augmentation uses WidgetCollectionAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in Augmentation uses a type in WidgetCollectionAttributeDefinitions.
- The types involved
Fabulous.AST.Augmentation.Augmentation→Fabulous.AST.WidgetCollectionAttributeDefinitions.WidgetCollectionAttributeDefinition
- Direction
- Augmentation uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break Augmentation, while a change to Augmentation can't break WidgetCollectionAttributeDefinitions.
- Position
- Below the diagonal: Augmentation uses a module listed above it, which is the healthy direction.
14→5 Augmentation uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in Augmentation uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.Augmentation.Augmentation→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- Augmentation uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Augmentation, while a change to Augmentation can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: Augmentation uses a module listed above it, which is the healthy direction.
15→1 AutoPropertyMember uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in AutoPropertyMember uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.AutoPropertyMember.AutoPropertyMember→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- AutoPropertyMember uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break AutoPropertyMember, while a change to AutoPropertyMember can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: AutoPropertyMember uses a module listed above it, which is the healthy direction.
15→3 AutoPropertyMember uses Fabulous.AST✕
- Connections
- 2 pairs of types, where a type in AutoPropertyMember uses a type in Fabulous.AST.
- The types involved
Fabulous.AST.AutoPropertyMember.AutoPropertyMember→Fabulous.AST.AccessControlFabulous.AST.AutoPropertyMember.AutoPropertyMember→Fabulous.AST.MethodParamsType
- Direction
- AutoPropertyMember uses Fabulous.AST, so a change to Fabulous.AST can break AutoPropertyMember, while a change to AutoPropertyMember can't break Fabulous.AST.
- Position
- Below the diagonal: AutoPropertyMember uses a module listed above it, which is the healthy direction.
15→5 AutoPropertyMember uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in AutoPropertyMember uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.AutoPropertyMember.AutoPropertyMember→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- AutoPropertyMember uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break AutoPropertyMember, while a change to AutoPropertyMember can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: AutoPropertyMember uses a module listed above it, which is the healthy direction.
16→1 BindingNode uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in BindingNode uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.BindingNode.BindingNode→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- BindingNode uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break BindingNode, while a change to BindingNode can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: BindingNode uses a module listed above it, which is the healthy direction.
16→3 BindingNode uses Fabulous.AST✕
- Connections
- 1 pair of types, where a type in BindingNode uses a type in Fabulous.AST.
- The types involved
Fabulous.AST.BindingNode.BindingNode→Fabulous.AST.AccessControl
- Direction
- BindingNode uses Fabulous.AST, so a change to Fabulous.AST can break BindingNode, while a change to BindingNode can't break Fabulous.AST.
- Position
- Below the diagonal: BindingNode uses a module listed above it, which is the healthy direction.
16→5 BindingNode uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in BindingNode uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.BindingNode.BindingNode→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- BindingNode uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break BindingNode, while a change to BindingNode can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: BindingNode uses a module listed above it, which is the healthy direction.
17→1 ChainLink uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in ChainLink uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.ChainLink.ChainLink→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- ChainLink uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break ChainLink, while a change to ChainLink can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: ChainLink uses a module listed above it, which is the healthy direction.
17→5 ChainLink uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in ChainLink uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.ChainLink.ChainLink→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- ChainLink uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break ChainLink, while a change to ChainLink can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: ChainLink uses a module listed above it, which is the healthy direction.
18→1 ComputationExpressionStatement uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in ComputationExpressionStatement uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.ComputationExpressionStatement.ComputationExpressionStatement→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- ComputationExpressionStatement uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break ComputationExpressionStatement, while a change to ComputationExpressionStatement can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: ComputationExpressionStatement uses a module listed above it, which is the healthy direction.
18→5 ComputationExpressionStatement uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in ComputationExpressionStatement uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.ComputationExpressionStatement.ComputationExpressionStatement→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- ComputationExpressionStatement uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break ComputationExpressionStatement, while a change to ComputationExpressionStatement can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: ComputationExpressionStatement uses a module listed above it, which is the healthy direction.
19→1 Delegate uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in Delegate uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.Delegate.Delegate→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- Delegate uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break Delegate, while a change to Delegate can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: Delegate uses a module listed above it, which is the healthy direction.
19→5 Delegate uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in Delegate uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.Delegate.Delegate→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- Delegate uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Delegate, while a change to Delegate can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: Delegate uses a module listed above it, which is the healthy direction.
20→1 DotNamedIndexedPropertySet uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in DotNamedIndexedPropertySet uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.DotNamedIndexedPropertySet.DotNamedIndexedPropertySet→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- DotNamedIndexedPropertySet uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break DotNamedIndexedPropertySet, while a change to DotNamedIndexedPropertySet can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: DotNamedIndexedPropertySet uses a module listed above it, which is the healthy direction.
20→5 DotNamedIndexedPropertySet uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in DotNamedIndexedPropertySet uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.DotNamedIndexedPropertySet.DotNamedIndexedPropertySet→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- DotNamedIndexedPropertySet uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break DotNamedIndexedPropertySet, while a change to DotNamedIndexedPropertySet can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: DotNamedIndexedPropertySet uses a module listed above it, which is the healthy direction.
21→2 Enum uses WidgetCollectionAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in Enum uses a type in WidgetCollectionAttributeDefinitions.
- The types involved
Fabulous.AST.Enum.Enum→Fabulous.AST.WidgetCollectionAttributeDefinitions.WidgetCollectionAttributeDefinition
- Direction
- Enum uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break Enum, while a change to Enum can't break WidgetCollectionAttributeDefinitions.
- Position
- Below the diagonal: Enum uses a module listed above it, which is the healthy direction.
21→5 Enum uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in Enum uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.Enum.Enum→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- Enum uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Enum, while a change to Enum can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: Enum uses a module listed above it, which is the healthy direction.
22→1 EnumCase uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in EnumCase uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.EnumCase.EnumCase→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- EnumCase uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break EnumCase, while a change to EnumCase can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: EnumCase uses a module listed above it, which is the healthy direction.
22→5 EnumCase uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in EnumCase uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.EnumCase.EnumCase→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- EnumCase uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break EnumCase, while a change to EnumCase can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: EnumCase uses a module listed above it, which is the healthy direction.
23→1 ExplicitConstructorMember uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in ExplicitConstructorMember uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.ExplicitConstructorMember.ExplicitConstructorMember→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- ExplicitConstructorMember uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break ExplicitConstructorMember, while a change to ExplicitConstructorMember can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: ExplicitConstructorMember uses a module listed above it, which is the healthy direction.
23→3 ExplicitConstructorMember uses Fabulous.AST✕
- Connections
- 1 pair of types, where a type in ExplicitConstructorMember uses a type in Fabulous.AST.
- The types involved
Fabulous.AST.ExplicitConstructorMember.ExplicitConstructorMember→Fabulous.AST.AccessControl
- Direction
- ExplicitConstructorMember uses Fabulous.AST, so a change to Fabulous.AST can break ExplicitConstructorMember, while a change to ExplicitConstructorMember can't break Fabulous.AST.
- Position
- Below the diagonal: ExplicitConstructorMember uses a module listed above it, which is the healthy direction.
23→5 ExplicitConstructorMember uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in ExplicitConstructorMember uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.ExplicitConstructorMember.ExplicitConstructorMember→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- ExplicitConstructorMember uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break ExplicitConstructorMember, while a change to ExplicitConstructorMember can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: ExplicitConstructorMember uses a module listed above it, which is the healthy direction.
24→1 ExternBinding uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in ExternBinding uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.ExternBinding.ExternBinding→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- ExternBinding uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break ExternBinding, while a change to ExternBinding can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: ExternBinding uses a module listed above it, which is the healthy direction.
24→3 ExternBinding uses Fabulous.AST✕
- Connections
- 1 pair of types, where a type in ExternBinding uses a type in Fabulous.AST.
- The types involved
Fabulous.AST.ExternBinding.ExternBinding→Fabulous.AST.AccessControl
- Direction
- ExternBinding uses Fabulous.AST, so a change to Fabulous.AST can break ExternBinding, while a change to ExternBinding can't break Fabulous.AST.
- Position
- Below the diagonal: ExternBinding uses a module listed above it, which is the healthy direction.
24→5 ExternBinding uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in ExternBinding uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.ExternBinding.ExternBinding→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- ExternBinding uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break ExternBinding, while a change to ExternBinding can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: ExternBinding uses a module listed above it, which is the healthy direction.
25→1 ExternBindingPattern uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in ExternBindingPattern uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.ExternBindingPattern.ExternBindingPattern→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- ExternBindingPattern uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break ExternBindingPattern, while a change to ExternBindingPattern can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: ExternBindingPattern uses a module listed above it, which is the healthy direction.
25→5 ExternBindingPattern uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in ExternBindingPattern uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.ExternBindingPattern.ExternBindingPattern→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- ExternBindingPattern uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break ExternBindingPattern, while a change to ExternBindingPattern can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: ExternBindingPattern uses a module listed above it, which is the healthy direction.
26→1 Field uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in Field uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.Field.Field→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- Field uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break Field, while a change to Field can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: Field uses a module listed above it, which is the healthy direction.
26→3 Field uses Fabulous.AST✕
- Connections
- 1 pair of types, where a type in Field uses a type in Fabulous.AST.
- The types involved
Fabulous.AST.Field.Field→Fabulous.AST.AccessControl
- Direction
- Field uses Fabulous.AST, so a change to Fabulous.AST can break Field, while a change to Field can't break Fabulous.AST.
- Position
- Below the diagonal: Field uses a module listed above it, which is the healthy direction.
26→5 Field uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in Field uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.Field.Field→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- Field uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Field, while a change to Field can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: Field uses a module listed above it, which is the healthy direction.
27→1 FillExprNode uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in FillExprNode uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.FillExprNode.FillExprNode→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- FillExprNode uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break FillExprNode, while a change to FillExprNode can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: FillExprNode uses a module listed above it, which is the healthy direction.
27→5 FillExprNode uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in FillExprNode uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.FillExprNode.FillExprNode→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- FillExprNode uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break FillExprNode, while a change to FillExprNode can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: FillExprNode uses a module listed above it, which is the healthy direction.
28→1 For uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in For uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.For.For→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- For uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break For, while a change to For can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: For uses a module listed above it, which is the healthy direction.
28→5 For uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in For uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.For.For→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- For uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break For, while a change to For can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: For uses a module listed above it, which is the healthy direction.
29→1 ImplicitConstructor uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in ImplicitConstructor uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.ImplicitConstructor.ImplicitConstructor→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- ImplicitConstructor uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break ImplicitConstructor, while a change to ImplicitConstructor can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: ImplicitConstructor uses a module listed above it, which is the healthy direction.
29→3 ImplicitConstructor uses Fabulous.AST✕
- Connections
- 1 pair of types, where a type in ImplicitConstructor uses a type in Fabulous.AST.
- The types involved
Fabulous.AST.ImplicitConstructor.ImplicitConstructor→Fabulous.AST.AccessControl
- Direction
- ImplicitConstructor uses Fabulous.AST, so a change to Fabulous.AST can break ImplicitConstructor, while a change to ImplicitConstructor can't break Fabulous.AST.
- Position
- Below the diagonal: ImplicitConstructor uses a module listed above it, which is the healthy direction.
29→5 ImplicitConstructor uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in ImplicitConstructor uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.ImplicitConstructor.ImplicitConstructor→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- ImplicitConstructor uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break ImplicitConstructor, while a change to ImplicitConstructor can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: ImplicitConstructor uses a module listed above it, which is the healthy direction.
30→1 MemberDefn uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in MemberDefn uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.MemberDefn.MemberDefn→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- MemberDefn uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break MemberDefn, while a change to MemberDefn can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: MemberDefn uses a module listed above it, which is the healthy direction.
30→3 MemberDefn uses Fabulous.AST✕
- Connections
- 1 pair of types, where a type in MemberDefn uses a type in Fabulous.AST.
- The types involved
Fabulous.AST.MemberDefn.MemberDefn→Fabulous.AST.AccessControl
- Direction
- MemberDefn uses Fabulous.AST, so a change to Fabulous.AST can break MemberDefn, while a change to MemberDefn can't break Fabulous.AST.
- Position
- Below the diagonal: MemberDefn uses a module listed above it, which is the healthy direction.
30→5 MemberDefn uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in MemberDefn uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.MemberDefn.MemberDefn→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- MemberDefn uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break MemberDefn, while a change to MemberDefn can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: MemberDefn uses a module listed above it, which is the healthy direction.
31→1 ModuleDecl uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in ModuleDecl uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.ModuleDecl.ModuleDecl→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- ModuleDecl uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break ModuleDecl, while a change to ModuleDecl can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: ModuleDecl uses a module listed above it, which is the healthy direction.
31→3 ModuleDecl uses Fabulous.AST✕
- Connections
- 1 pair of types, where a type in ModuleDecl uses a type in Fabulous.AST.
- The types involved
Fabulous.AST.ModuleDecl.ModuleDecl→Fabulous.AST.AccessControl
- Direction
- ModuleDecl uses Fabulous.AST, so a change to Fabulous.AST can break ModuleDecl, while a change to ModuleDecl can't break Fabulous.AST.
- Position
- Below the diagonal: ModuleDecl uses a module listed above it, which is the healthy direction.
31→5 ModuleDecl uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in ModuleDecl uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.ModuleDecl.ModuleDecl→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- ModuleDecl uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break ModuleDecl, while a change to ModuleDecl can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: ModuleDecl uses a module listed above it, which is the healthy direction.
32→1 ModuleOrNamespace uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in ModuleOrNamespace uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.ModuleOrNamespace.ModuleOrNamespace→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- ModuleOrNamespace uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break ModuleOrNamespace, while a change to ModuleOrNamespace can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: ModuleOrNamespace uses a module listed above it, which is the healthy direction.
32→2 ModuleOrNamespace uses WidgetCollectionAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in ModuleOrNamespace uses a type in WidgetCollectionAttributeDefinitions.
- The types involved
Fabulous.AST.ModuleOrNamespace.ModuleOrNamespace→Fabulous.AST.WidgetCollectionAttributeDefinitions.WidgetCollectionAttributeDefinition
- Direction
- ModuleOrNamespace uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break ModuleOrNamespace, while a change to ModuleOrNamespace can't break WidgetCollectionAttributeDefinitions.
- Position
- Below the diagonal: ModuleOrNamespace uses a module listed above it, which is the healthy direction.
32→3 ModuleOrNamespace uses Fabulous.AST✕
- Connections
- 1 pair of types, where a type in ModuleOrNamespace uses a type in Fabulous.AST.
- The types involved
Fabulous.AST.ModuleOrNamespace.ModuleOrNamespace→Fabulous.AST.AccessControl
- Direction
- ModuleOrNamespace uses Fabulous.AST, so a change to Fabulous.AST can break ModuleOrNamespace, while a change to ModuleOrNamespace can't break Fabulous.AST.
- Position
- Below the diagonal: ModuleOrNamespace uses a module listed above it, which is the healthy direction.
32→5 ModuleOrNamespace uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in ModuleOrNamespace uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.ModuleOrNamespace.ModuleOrNamespace→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- ModuleOrNamespace uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break ModuleOrNamespace, while a change to ModuleOrNamespace can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: ModuleOrNamespace uses a module listed above it, which is the healthy direction.
33→1 ObjExpr uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in ObjExpr uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.ObjExpr.ObjExpr→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- ObjExpr uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break ObjExpr, while a change to ObjExpr can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: ObjExpr uses a module listed above it, which is the healthy direction.
33→2 ObjExpr uses WidgetCollectionAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in ObjExpr uses a type in WidgetCollectionAttributeDefinitions.
- The types involved
Fabulous.AST.ObjExpr.ObjExpr→Fabulous.AST.WidgetCollectionAttributeDefinitions.WidgetCollectionAttributeDefinition
- Direction
- ObjExpr uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break ObjExpr, while a change to ObjExpr can't break WidgetCollectionAttributeDefinitions.
- Position
- Below the diagonal: ObjExpr uses a module listed above it, which is the healthy direction.
33→5 ObjExpr uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in ObjExpr uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.ObjExpr.ObjExpr→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- ObjExpr uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break ObjExpr, while a change to ObjExpr can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: ObjExpr uses a module listed above it, which is the healthy direction.
34→1 Pattern uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in Pattern uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.Pattern.Pattern→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- Pattern uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break Pattern, while a change to Pattern can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: Pattern uses a module listed above it, which is the healthy direction.
34→3 Pattern uses Fabulous.AST✕
- Connections
- 1 pair of types, where a type in Pattern uses a type in Fabulous.AST.
- The types involved
Fabulous.AST.Pattern.Pattern→Fabulous.AST.AccessControl
- Direction
- Pattern uses Fabulous.AST, so a change to Fabulous.AST can break Pattern, while a change to Pattern can't break Fabulous.AST.
- Position
- Below the diagonal: Pattern uses a module listed above it, which is the healthy direction.
34→5 Pattern uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in Pattern uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.Pattern.Pattern→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- Pattern uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Pattern, while a change to Pattern can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: Pattern uses a module listed above it, which is the healthy direction.
35→1 PropertyGetSetBinding uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in PropertyGetSetBinding uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.PropertyGetSetBinding.PropertyGetSetBinding→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- PropertyGetSetBinding uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break PropertyGetSetBinding, while a change to PropertyGetSetBinding can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: PropertyGetSetBinding uses a module listed above it, which is the healthy direction.
35→3 PropertyGetSetBinding uses Fabulous.AST✕
- Connections
- 1 pair of types, where a type in PropertyGetSetBinding uses a type in Fabulous.AST.
- The types involved
Fabulous.AST.PropertyGetSetBinding.PropertyGetSetBinding→Fabulous.AST.AccessControl
- Direction
- PropertyGetSetBinding uses Fabulous.AST, so a change to Fabulous.AST can break PropertyGetSetBinding, while a change to PropertyGetSetBinding can't break Fabulous.AST.
- Position
- Below the diagonal: PropertyGetSetBinding uses a module listed above it, which is the healthy direction.
35→5 PropertyGetSetBinding uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in PropertyGetSetBinding uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.PropertyGetSetBinding.PropertyGetSetBinding→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- PropertyGetSetBinding uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break PropertyGetSetBinding, while a change to PropertyGetSetBinding can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: PropertyGetSetBinding uses a module listed above it, which is the healthy direction.
36→1 TypeDefn uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in TypeDefn uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.TypeDefn.TypeDefn→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- TypeDefn uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break TypeDefn, while a change to TypeDefn can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: TypeDefn uses a module listed above it, which is the healthy direction.
36→2 TypeDefn uses WidgetCollectionAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in TypeDefn uses a type in WidgetCollectionAttributeDefinitions.
- The types involved
Fabulous.AST.TypeDefn.TypeDefn→Fabulous.AST.WidgetCollectionAttributeDefinitions.WidgetCollectionAttributeDefinition
- Direction
- TypeDefn uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break TypeDefn, while a change to TypeDefn can't break WidgetCollectionAttributeDefinitions.
- Position
- Below the diagonal: TypeDefn uses a module listed above it, which is the healthy direction.
36→3 TypeDefn uses Fabulous.AST✕
- Connections
- 1 pair of types, where a type in TypeDefn uses a type in Fabulous.AST.
- The types involved
Fabulous.AST.TypeDefn.TypeDefn→Fabulous.AST.AccessControl
- Direction
- TypeDefn uses Fabulous.AST, so a change to Fabulous.AST can break TypeDefn, while a change to TypeDefn can't break Fabulous.AST.
- Position
- Below the diagonal: TypeDefn uses a module listed above it, which is the healthy direction.
36→5 TypeDefn uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in TypeDefn uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.TypeDefn.TypeDefn→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- TypeDefn uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break TypeDefn, while a change to TypeDefn can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: TypeDefn uses a module listed above it, which is the healthy direction.
37→1 TypeDefnExplicit uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in TypeDefnExplicit uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.TypeDefnExplicit.TypeDefnExplicit→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- TypeDefnExplicit uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break TypeDefnExplicit, while a change to TypeDefnExplicit can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: TypeDefnExplicit uses a module listed above it, which is the healthy direction.
37→2 TypeDefnExplicit uses WidgetCollectionAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in TypeDefnExplicit uses a type in WidgetCollectionAttributeDefinitions.
- The types involved
Fabulous.AST.TypeDefnExplicit.TypeDefnExplicit→Fabulous.AST.WidgetCollectionAttributeDefinitions.WidgetCollectionAttributeDefinition
- Direction
- TypeDefnExplicit uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break TypeDefnExplicit, while a change to TypeDefnExplicit can't break WidgetCollectionAttributeDefinitions.
- Position
- Below the diagonal: TypeDefnExplicit uses a module listed above it, which is the healthy direction.
37→5 TypeDefnExplicit uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in TypeDefnExplicit uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.TypeDefnExplicit.TypeDefnExplicit→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- TypeDefnExplicit uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break TypeDefnExplicit, while a change to TypeDefnExplicit can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: TypeDefnExplicit uses a module listed above it, which is the healthy direction.
38→1 TypeDefnRegular uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in TypeDefnRegular uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.TypeDefnRegular.TypeDefnRegular→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- TypeDefnRegular uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break TypeDefnRegular, while a change to TypeDefnRegular can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: TypeDefnRegular uses a module listed above it, which is the healthy direction.
38→2 TypeDefnRegular uses WidgetCollectionAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in TypeDefnRegular uses a type in WidgetCollectionAttributeDefinitions.
- The types involved
Fabulous.AST.TypeDefnRegular.TypeDefnRegular→Fabulous.AST.WidgetCollectionAttributeDefinitions.WidgetCollectionAttributeDefinition
- Direction
- TypeDefnRegular uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break TypeDefnRegular, while a change to TypeDefnRegular can't break WidgetCollectionAttributeDefinitions.
- Position
- Below the diagonal: TypeDefnRegular uses a module listed above it, which is the healthy direction.
38→5 TypeDefnRegular uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in TypeDefnRegular uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.TypeDefnRegular.TypeDefnRegular→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- TypeDefnRegular uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break TypeDefnRegular, while a change to TypeDefnRegular can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: TypeDefnRegular uses a module listed above it, which is the healthy direction.
39→1 Val uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in Val uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.Val.Val→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- Val uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break Val, while a change to Val can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: Val uses a module listed above it, which is the healthy direction.
39→3 Val uses Fabulous.AST✕
- Connections
- 1 pair of types, where a type in Val uses a type in Fabulous.AST.
- The types involved
Fabulous.AST.Val.Val→Fabulous.AST.AccessControl
- Direction
- Val uses Fabulous.AST, so a change to Fabulous.AST can break Val, while a change to Val can't break Fabulous.AST.
- Position
- Below the diagonal: Val uses a module listed above it, which is the healthy direction.
39→5 Val uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in Val uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.Val.Val→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- Val uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Val, while a change to Val can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: Val uses a module listed above it, which is the healthy direction.
40→1 Widgets uses WidgetAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in Widgets uses a type in WidgetAttributeDefinitions.
- The types involved
Fabulous.AST.Widgets.Widgets→Fabulous.AST.WidgetAttributeDefinitions.WidgetAttributeDefinition
- Direction
- Widgets uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break Widgets, while a change to Widgets can't break WidgetAttributeDefinitions.
- Position
- Below the diagonal: Widgets uses a module listed above it, which is the healthy direction.
40→2 Widgets uses WidgetCollectionAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in Widgets uses a type in WidgetCollectionAttributeDefinitions.
- The types involved
Fabulous.AST.Widgets.Widgets→Fabulous.AST.WidgetCollectionAttributeDefinitions.WidgetCollectionAttributeDefinition
- Direction
- Widgets uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break Widgets, while a change to Widgets can't break WidgetCollectionAttributeDefinitions.
- Position
- Below the diagonal: Widgets uses a module listed above it, which is the healthy direction.
40→3 Widgets uses Fabulous.AST✕
- Connections
- 2 pairs of types, where a type in Widgets uses a type in Fabulous.AST.
- The types involved
Fabulous.AST.Widgets.Widgets→Fabulous.AST.WidgetFabulous.AST.Widgets.Widgets→Fabulous.AST.WidgetBuilder`1
- Direction
- Widgets uses Fabulous.AST, so a change to Fabulous.AST can break Widgets, while a change to Widgets can't break Fabulous.AST.
- Position
- Below the diagonal: Widgets uses a module listed above it, which is the healthy direction.
40→5 Widgets uses ScalarAttributeDefinitions✕
- Connections
- 1 pair of types, where a type in Widgets uses a type in ScalarAttributeDefinitions.
- The types involved
Fabulous.AST.Widgets.Widgets→Fabulous.AST.ScalarAttributeDefinitions.SimpleScalarAttributeDefinition`1
- Direction
- Widgets uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Widgets, while a change to Widgets can't break ScalarAttributeDefinitions.
- Position
- Below the diagonal: Widgets 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 |
|---|---|---|
| A05:2025 — Injection | 18 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 9 | Medium |
Roadmap
Top priorities: 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; 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; Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| 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. | +5.6 pts | Medium | Architecture documentation |
| Resolve the 1 Outdated finding(s) in Dependency Hygiene — start with Directory.Packages.props. | +1.4 pts | Low | Dependency Hygiene |
| 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. | +2.6 pts | Medium | Documentation (README) |
| Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it. | +2.4 pts | Medium | Deployment & Rollback |
| Reconcile the README with reality: README.md links to `LICENSE.md`, but `LICENSE.md` does not exist. | +1.7 pts | Medium | Documentation accuracy |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +0.5 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. | +0.5 pts | Low | Static Analysis (SAST) |
| Resolve the 11 Low coverage finding(s) in Code Coverage — start with MemberDefn.fs, ModuleDecl.fs, Rewrite.fs. | +0.4 pts | Medium | Code Coverage |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| src/Fabulous.AST/Rewrite/Rewrite.fs | 5.5 | Mixed | Cyclomatic Complexity: RewriteImpl.rewriteExpr (cyclomatic 118) |
| src/Fabulous.AST/Widgets/MemberDefinitions/MemberDefn.fs | 5.5 | Mixed | Code Duplication: Duplicated block (11 lines × 2) |
| src/Fabulous.AST/DSL/Array.fs | 5.9 | Mixed | Cyclomatic Complexity: StackList`1.replace (cyclomatic 19) |
| src/Fabulous.AST/Widgets/MemberDefinitions/AutoProperty.fs | 7.0 | Mixed | Code Duplication: Duplicated block (21 lines × 2) |
| src/Fabulous.AST/Widgets/Expressions/TraitCall.fs | 7.0 | Mixed | Code Duplication: Duplicated block (7–11 lines × 14) |
| src/Fabulous.AST/Widgets/Trivia.fs | 7.0 | Mixed | Code Duplication: Duplicated block (6 lines × 2) |
| src/Fabulous.AST/Widgets/MemberDefinitions/Default.fs | 7.1 | Mixed | Code Duplication: Duplicated block (16 lines × 3) |
| extensions/Fabulous.AST.Json/Parsing.fs | 7.4 | Mixed | Cyclomatic Complexity: Parsing.generateModule (cyclomatic 22) |
| src/Fabulous.AST/Widgets/MemberDefinitions/PropertyGetSetBinding.fs | 7.4 | Mixed | God Classes: TooManyFunctions: PropertyGetSetBindingBuilders |
| src/Fabulous.AST/Widgets/MemberDefinitions/AbstractSlot.fs | 7.4 | Mixed | Code Duplication: Duplicated block (29 lines × 2) |
| src/Fabulous.AST/Widgets/Expressions/Lambda.fs | 7.8 | Mixed | Code Duplication: Edited copy of a member (68 corresponding lines) |
| src/Fabulous.AST/Widgets/Patterns/As.fs | 7.8 | Mixed | Code Duplication: Edited copy of a member (57 corresponding lines) |
| src/Fabulous.AST/Widgets/TypeDefinitions/Augment.fs | 7.8 | Mixed | Code Duplication: Edited copy of a member (86 corresponding lines) |
| src/Fabulous.AST/Widgets/Expressions/StructTuple.fs | 7.8 | Mixed | Code Duplication: Edited copy of a member (34 corresponding lines) |
| src/Fabulous.AST/Widgets/MemberDefinitions/Method.fs | 7.8 | Mixed | Code Duplication: Duplicated block (24 lines × 2) |
| src/Fabulous.AST/Widgets/Patterns/LongIdent.fs | 7.8 | Mixed | Code Duplication: Duplicated block (18 lines × 2) |
| src/Fabulous.AST/Widgets/TypeDefinitions/TypeDefnExplicit.fs | 7.8 | Mixed | Code Duplication: Duplicated block (14 lines × 2) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 36 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 36 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, 141 of 161 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D15 Churn × Complexity Hotspots — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A hotspot's complexity is meant to be the worst body its churn actually touched. For src/Fabulous.AST/Rewrite/Rewrite.fs that could not be established — the complexity reader for the file reports no body extents, or the history carries no per-line attribution — so the row quotes the file's worst body, which the counted changes may never have touched. The churn count is unaffected.
- 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 (10 contributor(s) across 624 commit(s) sampled, automation and bot accounts excluded). One of them holds 91% of the history; the other 9 hold 1% 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.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is 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.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- 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.
- P8 Schema migrations — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads EF Core usage in C# and the schema tooling its file scan recognises only, and no .NET project was loaded, and this repository's language is not one the scan models, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X14 Bypassable address classification — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X15 Unvalidated length from an untrusted reader — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X26 Unsynchronised callback handoff — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X30 Support guard that admits what it rejects — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X32 Type resolved by simple name across every loaded assembly — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X6 Hand-rolled structured-format parsing — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Python, JavaScript/TypeScript, Go, Java/Kotlin/Scala, Ruby, PHP, Rust, Swift, Erlang, Elixir and Dart source only, and no C# was loaded and none of those languages was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X7 Silent fallback defaults — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift and Dart syntax only, and no C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift or Dart was loaded for this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
9 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was RewriteImpl.rewriteExpr at 118. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being StackArray3.combine at 16 — they are counted neither in the figure above nor in this dimension's score.
What to do
- Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with RewriteImpl.rewriteExpr (cyclomatic 118). — Refactoring it lifts Cyclomatic Complexity from 7.1 to about 7.8/10.
D2 · Cognitive Complexity
11 method(s) exceeded the cognitive complexity threshold of 15; the worst was RewriteImpl.rewriteExpr at 169.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with RewriteImpl.rewriteExpr (cognitive 169). — Refactoring it lifts Cognitive Complexity from 6.6 to about 7.7/10.
D3 · God Classes
3 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 TooManyFunctions finding(s) in God Classes — start with PropertyGetSetBinding.fs, AppPrefix.fs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with Rewrite.fs. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
68 duplicated block group(s) detected. 9.5 % of the production lines (2,268 of 23,846) are in a reported copy. A further 12 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 17 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with Trivia.fs (12), MemberDefn.fs (4), ObjExpr.fs. — One of this dimension's main actionable groups (17 warning-level).
- Resolve the 5 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with Builders.fs, _BindingNode.fs, Abbrev.fs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with ArrayOrList.fs, PropertyGetSetBinding.fs, Default.fs. — One of this dimension's main actionable groups (4 warning-level).
D5 · Coupling
5 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 1 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 70.7% — 11 file(s) below 50%.
What to do
- Resolve the 11 Low coverage finding(s) in Code Coverage — start with MemberDefn.fs, ModuleDecl.fs, Rewrite.fs. — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 1 No test project references Fabulous.AST.Build finding(s) in Code Coverage — start with Fabulous.AST.Build.fsproj. — One of this dimension's main actionable groups (1 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). unit: measured (0 flaky).
D12 · Dependency Hygiene
11 outdated, 0 vulnerable, 0 deprecated packages.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 136 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 11 direct `PackageReference`(s), and 126 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
Top hotspots: src/Fabulous.AST/Rewrite/Rewrite.fs (2×118=236)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with Rewrite.fs. — One of this dimension's main actionable groups (1 warning-level).
D26 · Project Cohesion
1 of 3 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
62 % of calls cross a namespace and 1 % 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)
18 finding(s): 0 critical, 17 high, 1 medium, 0 low. 15 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 2 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
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- No action in Static Analysis (SAST) — all 15 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 (15 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 101 of the 178 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- 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 — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 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
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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
M4 · Documentation accuracy
- README.md links to `LICENSE.md`, but `LICENSE.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:110
What to do
- Reconcile the README with reality: README.md links to `LICENSE.md`, but `LICENSE.md` does not exist.
P1 · CI/CD gates
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 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:2
- `Directory.Packages.props` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — Directory.Packages.props:6
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene
X28 · Index access outside its own emptiness guard
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 73% | Checked 4 of 11 | Strongest area. |
| Architecture | 95% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 55% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 59% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 67% | Checked 4 of 10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 1 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
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 — 76 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- 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.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No F# function in this code takes an ASP.NET Core or Suave HttpContext (a Giraffe, Saturn, Falco, Oxpecker or Suave handler) and no F# class is an ASP.NET Core controller, so no request handler shares module state between request threads.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — ~14595 lines of test source are present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- 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.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- 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 — N/A — too few peers to establish a naming convention (3958 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed F# surface was not measured.
- 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#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .fs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 18 value object(s); 4 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
- P2 Observability — This repository's F# source (3 module(s), 178 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
- P8 Schema migrations — 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
- P9 Domain vs controller coverage — coverage data present for 178 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- 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 scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X21 Side-effecting pattern guard — 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.
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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.
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X7 Silent fallback defaults — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 17 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 123 finding(s)
- Duplicated block (6 lines × 2) src/Fabulous.AST/Widgets/Expressions/ObjExpr.fs:152
- Duplicated block (6 lines × 2) src/Fabulous.AST/Widgets/MemberDefinitions/MemberDefn.fs:22
- Duplicated block (6 lines × 2) src/Fabulous.AST/Widgets/MemberDefinitions/MemberDefn.fs:41
- Duplicated block (6 lines × 2) src/Fabulous.AST/Widgets/MemberDefinitions/MemberDefn.fs:60
- Duplicated block (6 lines × 2) src/Fabulous.AST/Widgets/MemberDefinitions/MemberDefn.fs:79
- Duplicated block (6 lines × 2) src/Fabulous.AST/Widgets/Trivia.fs:311
- Duplicated block (6 lines × 2) src/Fabulous.AST/Widgets/Trivia.fs:335
- Duplicated block (6 lines × 2) src/Fabulous.AST/Widgets/Trivia.fs:476
- Duplicated block (6 lines × 2) src/Fabulous.AST/Widgets/Trivia.fs:500
- Duplicated block (6 lines × 2) src/Fabulous.AST/Widgets/Trivia.fs:641
- Duplicated block (6 lines × 2) src/Fabulous.AST/Widgets/Trivia.fs:665
- Duplicated block (6 lines × 2) src/Fabulous.AST/Widgets/Trivia.fs:806
- Duplicated block (6 lines × 2) src/Fabulous.AST/Widgets/Trivia.fs:830
- Duplicated block (6 lines × 2) src/Fabulous.AST/Widgets/Trivia.fs:969
- Duplicated block (6 lines × 2) src/Fabulous.AST/Widgets/Trivia.fs:991
- Duplicated block (6 lines × 2) src/Fabulous.AST/Widgets/Trivia.fs:1118
- Duplicated block (6 lines × 2) src/Fabulous.AST/Widgets/Trivia.fs:1140
- Low coverage: src/Fabulous.AST/Widgets/MemberDefinitions/MemberDefn.fs src/Fabulous.AST/Widgets/MemberDefinitions/MemberDefn.fs:1
- Low coverage: src/Fabulous.AST/Widgets/ModuleDeclarations/ModuleDecl.fs src/Fabulous.AST/Widgets/ModuleDeclarations/ModuleDecl.fs:1
- Low coverage: src/Fabulous.AST/Rewrite/Rewrite.fs src/Fabulous.AST/Rewrite/Rewrite.fs:1
- Low coverage: src/Fabulous.AST/Widgets/Types/WithSubTypeConstraint.fs src/Fabulous.AST/Widgets/Types/WithSubTypeConstraint.fs:1
- Low coverage: src/Fabulous.AST/Widgets/Types/LongIdentApp.fs src/Fabulous.AST/Widgets/Types/LongIdentApp.fs:1
- Low coverage: src/Fabulous.AST/Widgets/Expressions/ComputationExpressionStatement.fs src/Fabulous.AST/Widgets/Expressions/ComputationExpressionStatement.fs:1
- Low coverage: src/Fabulous.AST/Widgets/Expressions/JoinIn.fs src/Fabulous.AST/Widgets/Expressions/JoinIn.fs:1
- Low coverage: src/Fabulous.AST/Widgets/Expressions/Typar.fs src/Fabulous.AST/Widgets/Expressions/Typar.fs:1
- Low coverage: src/Fabulous.AST/Widgets/Expressions/TraitCall.fs src/Fabulous.AST/Widgets/Expressions/TraitCall.fs:1
- Low coverage: src/Fabulous.AST/DSL/Primitives.fs src/Fabulous.AST/DSL/Primitives.fs:1
- Low coverage: src/Fabulous.AST/DSL/Array.fs src/Fabulous.AST/DSL/Array.fs:1
- Duplicated block (9 lines × 2) src/Fabulous.AST/DSL/Builders.fs:193
- Duplicated block (9 lines × 2) src/Fabulous.AST/Widgets/MemberDefinitions/_BindingNode.fs:318
- Duplicated block (9 lines × 2) src/Fabulous.AST/Widgets/TypeDefinitions/Abbrev.fs:29
- Duplicated block (9 lines × 2) src/Fabulous.AST/Widgets/TypeDefinitions/Delegate.fs:49
- Duplicated block (9 lines × 2) src/Fabulous.AST/Widgets/Patterns/As.fs:9
- Duplicated block (7 lines × 2) src/Fabulous.AST/Widgets/Expressions/ArrayOrList.fs:38
- Duplicated block (7 lines × 2) src/Fabulous.AST/Widgets/MemberDefinitions/PropertyGetSetBinding.fs:261
- Duplicated block (7 lines × 2) src/Fabulous.AST/Widgets/MemberDefinitions/Default.fs:13
- Duplicated block (7 lines × 2) src/Fabulous.AST/Widgets/Expressions/Lambda.fs:9
- Duplicated block (11 lines × 2) src/Fabulous.AST/Widgets/MemberDefinitions/MemberDefn.fs:29
- Duplicated block (11 lines × 2) src/Fabulous.AST/Widgets/MemberDefinitions/MemberDefn.fs:48
- Duplicated block (11 lines × 2) src/Fabulous.AST/Widgets/MemberDefinitions/MemberDefn.fs:67
- Duplicated block (10 lines × 2) src/Fabulous.AST/DSL/Builders.fs:99
- Duplicated block (10 lines × 2) src/Fabulous.AST/Widgets/MemberDefinitions/Default.fs:58
- Duplicated block (10 lines × 2) src/Fabulous.AST/Widgets/Expressions/StructTuple.fs:8
- Duplicated block (8 lines × 2) src/Fabulous.AST/Widgets/MemberDefinitions/AbstractSlot.fs:220
- Duplicated block (8 lines × 2) src/Fabulous.AST/Widgets/MemberDefinitions/AbstractSlot.fs:366
- Duplicated block (8 lines × 2) src/Fabulous.AST/Widgets/MemberDefinitions/ExternBinding.fs:41
- TooManyFunctions: PropertyGetSetBindingBuilders src/Fabulous.AST/Widgets/MemberDefinitions/PropertyGetSetBinding.fs:80
- TooManyFunctions: TypeAppPrefixBuilders src/Fabulous.AST/Widgets/Types/AppPrefix.fs:45
- REDACTED
- REDACTED
- Duplicated block (18 lines × 2) src/Fabulous.AST/Widgets/Patterns/LongIdent.fs:17
- Duplicated block (18 lines × 2) src/Fabulous.AST/Widgets/TypeDefinitions/Record.fs:56
- Duplicated block (15 lines × 2) src/Fabulous.AST/Widgets/MemberDefinitions/Default.fs:35
- Duplicated block (15 lines × 2) src/Fabulous.AST/Widgets/ModuleDeclarations/Open.fs:31
- Duplicated block (12 lines × 2) src/Fabulous.AST/Widgets/MemberDefinitions/AutoProperty.fs:266
- Duplicated block (12 lines × 2) src/Fabulous.AST/Widgets/MemberDefinitions/Field.fs:45
- Duplicated block (10 lines × 4) src/Fabulous.AST/Widgets/MemberDefinitions/AutoProperty.fs:29
- Duplicated block (10 lines × 4) src/Fabulous.AST/Widgets/MemberDefinitions/AutoProperty.fs:224
- Duplicated block (5 lines × 2) src/Fabulous.AST/Widgets/Expressions/For.fs:45
- Duplicated block (5 lines × 2) src/Fabulous.AST/Widgets/Trivia.fs:178
- RewriteImpl.rewriteExpr (cyclomatic 118) src/Fabulous.AST/Rewrite/Rewrite.fs:46
- RewriteImpl.rewriteType (cyclomatic 40) src/Fabulous.AST/Rewrite/Rewrite.fs:293
- RewriteImpl.rewritePattern (cyclomatic 31) src/Fabulous.AST/Rewrite/Rewrite.fs:241
- RewriteImpl.rewriteMemberDefn (cyclomatic 27) src/Fabulous.AST/Rewrite/Rewrite.fs:354
- Parsing.generateModule (cyclomatic 22) extensions/Fabulous.AST.Json/Parsing.fs:341
- RewriteImpl.rewriteModuleDecl (cyclomatic 19) src/Fabulous.AST/Rewrite/Rewrite.fs:396
- RewriteImpl.rewriteTypeDefn (cyclomatic 19) src/Fabulous.AST/Rewrite/Rewrite.fs:426
- StackList`1.replace (cyclomatic 19) src/Fabulous.AST/DSL/Array.fs:207
- StackArray3.sortInPlace (cyclomatic 17) src/Fabulous.AST/DSL/Array.fs:319
- Hotspot: src/Fabulous.AST/Rewrite/Rewrite.fs src/Fabulous.AST/Rewrite/Rewrite.fs:46
- RewriteImpl.rewriteExpr (cognitive 169) src/Fabulous.AST/Rewrite/Rewrite.fs:46
- RewriteImpl.rewriteType (cognitive 55) src/Fabulous.AST/Rewrite/Rewrite.fs:293
- RewriteImpl.rewritePattern (cognitive 43) src/Fabulous.AST/Rewrite/Rewrite.fs:241
- RewriteImpl.rewriteMemberDefn (cognitive 40) src/Fabulous.AST/Rewrite/Rewrite.fs:354
- Parsing.generateModule (cognitive 36) extensions/Fabulous.AST.Json/Parsing.fs:341
- RewriteImpl.rewriteTypeDefn (cognitive 28) src/Fabulous.AST/Rewrite/Rewrite.fs:426
- RewriteImpl.rewriteModuleDecl (cognitive 25) src/Fabulous.AST/Rewrite/Rewrite.fs:396
- Parsing.toPascalCase (cognitive 17) extensions/Fabulous.AST.Json/Parsing.fs:17
- RewriteImpl.rewriteTypeConstraint (cognitive 16) src/Fabulous.AST/Rewrite/Rewrite.fs:456
- RewriteImpl.rewriteChainLink (cognitive 16) src/Fabulous.AST/Rewrite/Rewrite.fs:507
- StackList`1.replace (cognitive 16) src/Fabulous.AST/DSL/Array.fs:207
- REDACTED
- FileTooLong: Rewrite/Rewrite.fs src/Fabulous.AST/Rewrite/Rewrite.fs
- REDACTED
- REDACTED
- REDACTED
- Edited copies of one member (3 members, 135+ corresponding lines) src/Fabulous.AST/Widgets/Expressions/DotIndexedSet.fs:1
- Edited copy of a member (68 corresponding lines) src/Fabulous.AST/Widgets/Expressions/Lambda.fs:1
- Edited copy of a member (57 corresponding lines) src/Fabulous.AST/Widgets/Patterns/As.fs:1
- Edited copy of a member (59 corresponding lines) src/Fabulous.AST/Widgets/Expressions/TryFinally.fs:1
- Edited copy of a member (86 corresponding lines) src/Fabulous.AST/Widgets/TypeDefinitions/Augment.fs:1
- Edited copy of a member (38 corresponding lines) src/Fabulous.AST/Widgets/Expressions/IndexWithoutDot.fs:1
- Edited copy of a member (37 corresponding lines) src/Fabulous.AST/Widgets/Expressions/LongIdentSet.fs:1
- Edited copy of a member (34 corresponding lines) src/Fabulous.AST/Widgets/Expressions/StructTuple.fs:1
- Edited copy of a member (35 corresponding lines) src/Fabulous.AST/Widgets/Patterns/Named.fs:1
- Edited copies of one member (3 members, 28+ corresponding lines) src/Fabulous.AST/Widgets/Patterns/Ands.fs:1
- Edited copies of one member (3 members, 24+ corresponding lines) src/Fabulous.AST/Widgets/Expressions/Paren.fs:1
- Edited copies of one member (4 members, 19+ corresponding lines) src/Fabulous.AST/Widgets/Expressions/Ident.fs:1
- Duplicated block (29 lines × 2) src/Fabulous.AST/Widgets/MemberDefinitions/AbstractSlot.fs:252
- Duplicated block (7–27 lines × 2) src/Fabulous.AST/Widgets/MemberDefinitions/PropertyGetSetBinding.fs:268
- Duplicated block (24 lines × 2) src/Fabulous.AST/Widgets/MemberDefinitions/Method.fs:17
- Duplicated block (20–22 lines × 2) src/Fabulous.AST/Widgets/MemberDefinitions/Method.fs:58
- Duplicated block (21 lines × 2) src/Fabulous.AST/Widgets/MemberDefinitions/AutoProperty.fs:31
- Duplicated block (20 lines × 2) src/Fabulous.AST/Widgets/MemberDefinitions/Function.fs:26
- Duplicated block (14–18 lines × 2) src/Fabulous.AST/Rewrite/Rewrite.fs:864
- Duplicated block (16 lines × 4) src/Fabulous.AST/Widgets/MemberDefinitions/AutoProperty.fs:310
- Duplicated block (16 lines × 3) src/Fabulous.AST/Widgets/MemberDefinitions/Default.fs:23
- Duplicated block (9–15 lines × 3) src/Fabulous.AST/Widgets/MemberDefinitions/AutoProperty.fs:147
- Duplicated block (14 lines × 2) src/Fabulous.AST/Widgets/TypeDefinitions/TypeDefnExplicit.fs:37
- Duplicated block (10–12 lines × 7) src/Fabulous.AST/Widgets/MemberDefinitions/AutoProperty.fs:27
- Duplicated block (9–12 lines × 7) src/Fabulous.AST/Widgets/MemberDefinitions/AutoProperty.fs:146
- Duplicated block (10–12 lines × 4) src/Fabulous.AST/Widgets/MemberDefinitions/ExternBinding.fs:39
- Duplicated block (10–12 lines × 2) src/Fabulous.AST/Widgets/ModuleDeclarations/Exception.fs:25
- Duplicated block (7–11 lines × 14) src/Fabulous.AST/Widgets/Expressions/TraitCall.fs:31
- Duplicated block (9–11 lines × 3) src/Fabulous.AST/Widgets/TypeDefinitions/TypeDefnExplicit.fs:43
- Duplicated block (9–10 lines × 4) src/Fabulous.AST/Widgets/TypeDefinitions/Augment.fs:34
- Duplicated block (10 lines × 3) src/Fabulous.AST/Widgets/Patterns/LongIdent.fs:39
- Duplicated block (9 lines × 9) src/Fabulous.AST/Widgets/MemberDefinitions/AutoProperty.fs:146
- Duplicated block (8 lines × 13) src/Fabulous.AST/Widgets/MemberDefinitions/AutoProperty.fs:29
- Duplicated block (8 lines × 8) src/Fabulous.AST/Widgets/MemberDefinitions/Default.fs:21
- Duplicated block (8 lines × 4) src/Fabulous.AST/Widgets/Expressions/ObjExpr.fs:127
- No test project references Fabulous.AST.Build extensions/Fabulous.AST.Build/Fabulous.AST.Build.fsproj
- Test suite runs only after the merge
Minor — 11 finding(s)
- Outdated: Verify.XunitV3 Directory.Packages.props:11
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- README/code drift README.md:110
- No SAST REDACTED:2
- No dependency-update automation Directory.Packages.props:6
Minor — 10 finding(s)
- Outdated: Fantomas.Core
- Outdated: FSharp.Core
- Outdated: FsCheck
- Outdated: FsCheck.Xunit
- Outdated: FsUnit.xUnit
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: xunit.runner.visualstudio
- Outdated: xunit.v3
- Outdated: Microsoft.Build.Framework
- Outdated: Microsoft.Build.Utilities.Core
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-2fcc6b4556514982b736d8bc1c62bb63/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-2fcc6b4556514982b736d8bc1c62bb63/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude samples/Playground/Generated . | 18 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list Fabulous.AST.sln package --vulnerable --include-transitive --format json | 0 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-d3c90e81ab7e432397c7e4d9f39d704f | 0 | artifacts/raw/osv-scanner.json |