Executive summary
fsprojects/FSharpLint falls short of our standard for a preview release, in part because we found no logging, tracing or health checks in the code. It scores 57 out of 100 and is rated Adequate, and all 22 of its critical findings are security problems.
Production Readiness, at 48, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 5 points. Adding a diagnostic log would lift Production Readiness itself, worth about 6 points. Raising Production Readiness to 62 would lift the score to about 63.
Fifteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two known security holes in the packages the code depends on can be used by attackers, and two pipeline steps install packages that can change without warning. Pinning each tool to an exact version, updating the vulnerable packages and pinning what the pipeline installs would close these risks. Limiting each secret to its own step would fix the two secrets exposed to more of the pipeline than needed, and the password or key in the code's history needs replacing, with the old one switched off.
The product code is 11,666 lines, about €37,000 to rebuild.
If Production Readiness rose from 48 to 62, the lowest score rated Strong, the score would rise from 57 to about 63.
New since the last survey: 11 findings
- Cyclomatic Complexity · NoMutatorFunctions.runner (cyclomatic 19) src/FSharpLint.Core/Rules/Conventions/NoMutatorFunctions.fs
- Cognitive Complexity · NoMutatorFunctions.runner (cognitive 28) src/FSharpLint.Core/Rules/Conventions/NoMutatorFunctions.fs
- Cognitive Complexity · FavourSingleton.runner (cognitive 25) src/FSharpLint.Core/Rules/Conventions/FavourSingleton.fs
- Code Duplication · Edited copy of a member (53 corresponding lines) src/FSharpLint.Core/Rules/Conventions/Naming/PrivateValuesNames.fs
- Code Duplication · Edited copy of a member (57 corresponding lines) src/FSharpLint.Core/Rules/Formatting/Spacing/ClassMemberSpacing.fs
- Code Duplication · Edited copy of a member (39 corresponding lines) src/FSharpLint.Core/Rules/Formatting/PatternMatchFormatting/PatternMatchClausesOnNewLine.fs
- Code Duplication · Edited copy of a member (29 corresponding lines) src/FSharpLint.Core/Rules/Conventions/Naming/NestedFunctionNames.fs
- Code Duplication · Edited copy of a member (24 corresponding lines) src/FSharpLint.Core/Rules/Conventions/Naming/ModuleNames.fs
- Code Duplication · Edited copies of one member (3 members, 19+ corresponding lines) src/FSharpLint.Core/Rules/Conventions/Naming/EnumCasesNames.fs
- Code Duplication · Edited copies of one member (3 members, 21+ corresponding lines) src/FSharpLint.Core/Rules/Conventions/SourceLength/MaxLinesInLambdaFunction.fs
- Churn × Complexity Hotspots · Hotspot: src/FSharpLint.Core/Rules/Conventions/NoMutatorFunctions.fs src/FSharpLint.Core/Rules/Conventions/NoMutatorFunctions.fs
Fixed since the last survey: 13 findings
- Cyclomatic Complexity · jquery.sticky.scroller (cyclomatic 21) docs/static/js/jquery.sticky.js
- Cognitive Complexity · jquery.sticky.scroller (cognitive 44) docs/static/js/jquery.sticky.js
- God Classes · FunctionTooLong: jquery.sticky.scroller docs/static/js/jquery.sticky.js
- Code Coverage · Coverage not measured — no coverage collector is wired up
- Churn × Complexity Hotspots · Hotspot: src/FSharpLint.Core/Framework/AbstractSyntaxArray.fs src/FSharpLint.Core/Framework/AbstractSyntaxArray.fs
- Churn × Complexity Hotspots · Hotspot: src/FSharpLint.Core/Framework/Ast.fs src/FSharpLint.Core/Framework/Ast.fs
- Churn × Complexity Hotspots · Hotspot: src/FSharpLint.Core/Rules/Conventions/NoPartialFunctions.fs src/FSharpLint.Core/Rules/Conventions/NoPartialFunctions.fs
- Churn × Complexity Hotspots · Hotspot: src/FSharpLint.Core/Rules/Conventions/Naming/SimpleAsyncComplementaryHelpers.fs src/FSharpLint.Core/Rules/Conventions/Naming/SimpleAsyncComplementaryHelpers.fs
- Churn × Complexity Hotspots · Hotspot: src/FSharpLint.Core/Rules/Hints/HintMatcher.fs src/FSharpLint.Core/Rules/Hints/HintMatcher.fs
- Churn × Complexity Hotspots · Hotspot: src/FSharpLint.Core/Rules/NamingHelper.fs src/FSharpLint.Core/Rules/NamingHelper.fs
- Churn × Complexity Hotspots · Hotspot: src/FSharpLint.Core/Rules/Conventions/Naming/AvoidTooShortNames.fs src/FSharpLint.Core/Rules/Conventions/Naming/AvoidTooShortNames.fs
- Platform End-of-Life · End-of-life runtime: .NET net9.0 tests/FSharpLint.FunctionalTest/FSharpLint.FunctionalTest.fsproj
- Documentation (README) · README may be stale
Rebuild cost: about €37,000 · Estimate
| Cost to rebuild | €12,000 to €62,000, for 205 to 651 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 57. 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 | Small: 11,666 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 Framework.Ast | 2 Framework.HintParserTypes | 3 Framework.Suggestion | 4 Rules.Helper.NumberOfItems | 5 Framework.AbstractSyntaxArray | 6 Framework.MergeSyntaxTrees | 7 Rules.Helper.SourceLength | 8 Framework.Rules | 9 Rules.AsynchronousFunctionNames | 10 Rules.AvoidSinglePipeOperator | 11 Rules.CyclomaticComplexity | 12 Rules.FavourConsistentThis | 13 Rules.HintMatcher | 14 Rules.IndexerAccessorStyleConsistency | 15 Rules.MaxCharactersOnLine | 16 Rules.MaxLinesInClass | 17 Rules.MaxLinesInConstructor | 18 Rules.MaxLinesInEnum | 19 Rules.MaxLinesInFile | 20 Rules.MaxLinesInFunction | 21 Rules.MaxLinesInLambdaFunction | 22 Rules.MaxLinesInMatchLambdaFunction | 23 Rules.MaxLinesInMember | 24 Rules.MaxLinesInModule | 25 Rules.MaxLinesInProperty | 26 Rules.MaxLinesInRecord | 27 Rules.MaxLinesInUnion | 28 Rules.MaxLinesInValue | 29 Rules.MaxNumberOfItemsInTuple | 30 Rules.NestedStatements | 31 Rules.NoAsyncRunSynchronouslyInLibrary | 32 Rules.PatternMatchClauseIndentation | 33 Rules.RecursiveAsyncFunction | 34 Rules.SimpleAsyncComplementaryHelpers | 35 Rules.TrailingWhitespaceOnLine | 36 Rules.TupleParentheses | 37 Rules.TypePrefixing | 38 Framework.Configuration | 39 Rules.HintMatcher.FormatHint | 40 Application.Lint |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Framework.Ast | ||||||||||||||||||||||||||||||||||||||||
| 2 Framework.HintParserTypes | ||||||||||||||||||||||||||||||||||||||||
| 3 Framework.Suggestion | ||||||||||||||||||||||||||||||||||||||||
| 4 Rules.Helper.NumberOfItems | ||||||||||||||||||||||||||||||||||||||||
| 5 Framework.AbstractSyntaxArray | 5 | |||||||||||||||||||||||||||||||||||||||
| 6 Framework.MergeSyntaxTrees | 9 | |||||||||||||||||||||||||||||||||||||||
| 7 Rules.Helper.SourceLength | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 Framework.Rules | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 9 Rules.AsynchronousFunctionNames | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 10 Rules.AvoidSinglePipeOperator | 2 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 11 Rules.CyclomaticComplexity | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 12 Rules.FavourConsistentThis | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 13 Rules.HintMatcher | 3 | 5 | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 14 Rules.IndexerAccessorStyleConsistency | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 15 Rules.MaxCharactersOnLine | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 16 Rules.MaxLinesInClass | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 17 Rules.MaxLinesInConstructor | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 18 Rules.MaxLinesInEnum | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 19 Rules.MaxLinesInFile | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 20 Rules.MaxLinesInFunction | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 21 Rules.MaxLinesInLambdaFunction | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 22 Rules.MaxLinesInMatchLambdaFunction | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 23 Rules.MaxLinesInMember | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 24 Rules.MaxLinesInModule | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 25 Rules.MaxLinesInProperty | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 26 Rules.MaxLinesInRecord | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 27 Rules.MaxLinesInUnion | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 28 Rules.MaxLinesInValue | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 29 Rules.MaxNumberOfItemsInTuple | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 30 Rules.NestedStatements | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 31 Rules.NoAsyncRunSynchronouslyInLibrary | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 32 Rules.PatternMatchClauseIndentation | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 33 Rules.RecursiveAsyncFunction | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 34 Rules.SimpleAsyncComplementaryHelpers | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 35 Rules.TrailingWhitespaceOnLine | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 36 Rules.TupleParentheses | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 37 Rules.TypePrefixing | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 38 Framework.Configuration | 1 | 1 | 20 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||
| 39 Rules.HintMatcher.FormatHint | 1 | 3 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 Application.Lint | 3 | 1 | 4 | 3 |
5→1 Framework.AbstractSyntaxArray uses Framework.Ast✕
- Connections
- 5 pairs of types, where a type in Framework.AbstractSyntaxArray uses a type in Framework.Ast.
- The types involved
FSharpLint.Framework.AbstractSyntaxArray.AbstractSyntaxArray→FSharpLint.Framework.Ast.AstNodeFSharpLint.Framework.AbstractSyntaxArray.CurrentNode→FSharpLint.Framework.Ast.AstNodeFSharpLint.Framework.AbstractSyntaxArray.Node→FSharpLint.Framework.Ast.AstNodeFSharpLint.Framework.AbstractSyntaxArray.StackedNode→FSharpLint.Framework.Ast.AstNodeFSharpLint.Framework.AbstractSyntaxArray.TempNode→FSharpLint.Framework.Ast.AstNode
- Direction
- Framework.AbstractSyntaxArray uses Framework.Ast, so a change to Framework.Ast can break Framework.AbstractSyntaxArray, while a change to Framework.AbstractSyntaxArray can't break Framework.Ast.
- Position
- Below the diagonal: Framework.AbstractSyntaxArray uses a module listed above it, which is the healthy direction.
6→2 Framework.MergeSyntaxTrees uses Framework.HintParserTypes✕
- Connections
- 9 pairs of types, where a type in Framework.MergeSyntaxTrees uses a type in Framework.HintParserTypes.
- The types involved
FSharpLint.Framework.MergeSyntaxTrees.BuildState→FSharpLint.Framework.HintParserTypes.HintFSharpLint.Framework.MergeSyntaxTrees.MergeSyntaxTrees→FSharpLint.Framework.HintParserTypes.ConstantFSharpLint.Framework.MergeSyntaxTrees.MergeSyntaxTrees→FSharpLint.Framework.HintParserTypes.ExpressionFSharpLint.Framework.MergeSyntaxTrees.MergeSyntaxTrees→FSharpLint.Framework.HintParserTypes.HintFSharpLint.Framework.MergeSyntaxTrees.MergeSyntaxTrees→FSharpLint.Framework.HintParserTypes.HintNodeFSharpLint.Framework.MergeSyntaxTrees.MergeSyntaxTrees→FSharpLint.Framework.HintParserTypes.PatternFSharpLint.Framework.MergeSyntaxTrees.Node→FSharpLint.Framework.HintParserTypes.HintFSharpLint.Framework.MergeSyntaxTrees.TransposedNode→FSharpLint.Framework.HintParserTypes.HintFSharpLint.Framework.MergeSyntaxTrees.TransposedNode→FSharpLint.Framework.HintParserTypes.HintNode
- Direction
- Framework.MergeSyntaxTrees uses Framework.HintParserTypes, so a change to Framework.HintParserTypes can break Framework.MergeSyntaxTrees, while a change to Framework.MergeSyntaxTrees can't break Framework.HintParserTypes.
- Position
- Below the diagonal: Framework.MergeSyntaxTrees uses a module listed above it, which is the healthy direction.
7→3 Rules.Helper.SourceLength uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.Helper.SourceLength uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.Helper.SourceLength.SourceLength→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.Helper.SourceLength uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.Helper.SourceLength, while a change to Rules.Helper.SourceLength can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.Helper.SourceLength uses a module listed above it, which is the healthy direction.
8→1 Framework.Rules uses Framework.Ast✕
- Connections
- 1 pair of types, where a type in Framework.Rules uses a type in Framework.Ast.
- The types involved
FSharpLint.Framework.Rules.AstNodeRuleParams→FSharpLint.Framework.Ast.AstNode
- Direction
- Framework.Rules uses Framework.Ast, so a change to Framework.Ast can break Framework.Rules, while a change to Framework.Rules can't break Framework.Ast.
- Position
- Below the diagonal: Framework.Rules uses a module listed above it, which is the healthy direction.
8→3 Framework.Rules uses Framework.Suggestion✕
- Connections
- 2 pairs of types, where a type in Framework.Rules uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Framework.Rules.Rules→FSharpLint.Framework.Suggestion.LintWarningFSharpLint.Framework.Rules.Rules→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Framework.Rules uses Framework.Suggestion, so a change to Framework.Suggestion can break Framework.Rules, while a change to Framework.Rules can't break Framework.Suggestion.
- Position
- Below the diagonal: Framework.Rules uses a module listed above it, which is the healthy direction.
8→5 Framework.Rules uses Framework.AbstractSyntaxArray✕
- Connections
- 1 pair of types, where a type in Framework.Rules uses a type in Framework.AbstractSyntaxArray.
- The types involved
FSharpLint.Framework.Rules.AstNodeRuleParams→FSharpLint.Framework.AbstractSyntaxArray.Node
- Direction
- Framework.Rules uses Framework.AbstractSyntaxArray, so a change to Framework.AbstractSyntaxArray can break Framework.Rules, while a change to Framework.Rules can't break Framework.AbstractSyntaxArray.
- Position
- Below the diagonal: Framework.Rules uses a module listed above it, which is the healthy direction.
9→3 Rules.AsynchronousFunctionNames uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.AsynchronousFunctionNames uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.AsynchronousFunctionNames.AsynchronousFunctionNames→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.AsynchronousFunctionNames uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.AsynchronousFunctionNames, while a change to Rules.AsynchronousFunctionNames can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.AsynchronousFunctionNames uses a module listed above it, which is the healthy direction.
9→8 Rules.AsynchronousFunctionNames uses Framework.Rules✕
- Connections
- 2 pairs of types, where a type in Rules.AsynchronousFunctionNames uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.AsynchronousFunctionNames.AsynchronousFunctionNames→FSharpLint.Framework.Rules.AstNodeRuleParamsFSharpLint.Rules.AsynchronousFunctionNames.AsynchronousFunctionNames→FSharpLint.Framework.Rules.Rule
- Direction
- Rules.AsynchronousFunctionNames uses Framework.Rules, so a change to Framework.Rules can break Rules.AsynchronousFunctionNames, while a change to Rules.AsynchronousFunctionNames can't break Framework.Rules.
- Position
- Below the diagonal: Rules.AsynchronousFunctionNames uses a module listed above it, which is the healthy direction.
10→1 Rules.AvoidSinglePipeOperator uses Framework.Ast✕
- Connections
- 2 pairs of types, where a type in Rules.AvoidSinglePipeOperator uses a type in Framework.Ast.
- The types involved
FSharpLint.Rules.AvoidSinglePipeOperator.AvoidSinglePipeOperator→FSharpLint.Framework.Ast.AstNodeFSharpLint.Rules.AvoidSinglePipeOperator.CheckExprContinuationPassingStyleArgs→FSharpLint.Framework.Ast.AstNode
- Direction
- Rules.AvoidSinglePipeOperator uses Framework.Ast, so a change to Framework.Ast can break Rules.AvoidSinglePipeOperator, while a change to Rules.AvoidSinglePipeOperator can't break Framework.Ast.
- Position
- Below the diagonal: Rules.AvoidSinglePipeOperator uses a module listed above it, which is the healthy direction.
10→3 Rules.AvoidSinglePipeOperator uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.AvoidSinglePipeOperator uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.AvoidSinglePipeOperator.AvoidSinglePipeOperator→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.AvoidSinglePipeOperator uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.AvoidSinglePipeOperator, while a change to Rules.AvoidSinglePipeOperator can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.AvoidSinglePipeOperator uses a module listed above it, which is the healthy direction.
10→8 Rules.AvoidSinglePipeOperator uses Framework.Rules✕
- Connections
- 3 pairs of types, where a type in Rules.AvoidSinglePipeOperator uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.AvoidSinglePipeOperator.AvoidSinglePipeOperator→FSharpLint.Framework.Rules.AstNodeRuleParamsFSharpLint.Rules.AvoidSinglePipeOperator.AvoidSinglePipeOperator→FSharpLint.Framework.Rules.RuleFSharpLint.Rules.AvoidSinglePipeOperator.CheckExprContinuationPassingStyleArgs→FSharpLint.Framework.Rules.AstNodeRuleParams
- Direction
- Rules.AvoidSinglePipeOperator uses Framework.Rules, so a change to Framework.Rules can break Rules.AvoidSinglePipeOperator, while a change to Rules.AvoidSinglePipeOperator can't break Framework.Rules.
- Position
- Below the diagonal: Rules.AvoidSinglePipeOperator uses a module listed above it, which is the healthy direction.
11→1 Rules.CyclomaticComplexity uses Framework.Ast✕
- Connections
- 1 pair of types, where a type in Rules.CyclomaticComplexity uses a type in Framework.Ast.
- The types involved
FSharpLint.Rules.CyclomaticComplexity.BindingScope→FSharpLint.Framework.Ast.AstNode
- Direction
- Rules.CyclomaticComplexity uses Framework.Ast, so a change to Framework.Ast can break Rules.CyclomaticComplexity, while a change to Rules.CyclomaticComplexity can't break Framework.Ast.
- Position
- Below the diagonal: Rules.CyclomaticComplexity uses a module listed above it, which is the healthy direction.
11→3 Rules.CyclomaticComplexity uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.CyclomaticComplexity uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.CyclomaticComplexity.CyclomaticComplexity→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.CyclomaticComplexity uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.CyclomaticComplexity, while a change to Rules.CyclomaticComplexity can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.CyclomaticComplexity uses a module listed above it, which is the healthy direction.
11→8 Rules.CyclomaticComplexity uses Framework.Rules✕
- Connections
- 3 pairs of types, where a type in Rules.CyclomaticComplexity uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.CyclomaticComplexity.BindingStack→FSharpLint.Framework.Rules.AstNodeRuleParamsFSharpLint.Rules.CyclomaticComplexity.CyclomaticComplexity→FSharpLint.Framework.Rules.AstNodeRuleParamsFSharpLint.Rules.CyclomaticComplexity.CyclomaticComplexity→FSharpLint.Framework.Rules.Rule
- Direction
- Rules.CyclomaticComplexity uses Framework.Rules, so a change to Framework.Rules can break Rules.CyclomaticComplexity, while a change to Rules.CyclomaticComplexity can't break Framework.Rules.
- Position
- Below the diagonal: Rules.CyclomaticComplexity uses a module listed above it, which is the healthy direction.
12→3 Rules.FavourConsistentThis uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.FavourConsistentThis uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.FavourConsistentThis.FavourConsistentThis→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.FavourConsistentThis uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.FavourConsistentThis, while a change to Rules.FavourConsistentThis can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.FavourConsistentThis uses a module listed above it, which is the healthy direction.
12→8 Rules.FavourConsistentThis uses Framework.Rules✕
- Connections
- 2 pairs of types, where a type in Rules.FavourConsistentThis uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.FavourConsistentThis.FavourConsistentThis→FSharpLint.Framework.Rules.AstNodeRuleParamsFSharpLint.Rules.FavourConsistentThis.FavourConsistentThis→FSharpLint.Framework.Rules.Rule
- Direction
- Rules.FavourConsistentThis uses Framework.Rules, so a change to Framework.Rules can break Rules.FavourConsistentThis, while a change to Rules.FavourConsistentThis can't break Framework.Rules.
- Position
- Below the diagonal: Rules.FavourConsistentThis uses a module listed above it, which is the healthy direction.
13→1 Rules.HintMatcher uses Framework.Ast✕
- Connections
- 3 pairs of types, where a type in Rules.HintMatcher uses a type in Framework.Ast.
- The types involved
FSharpLint.Rules.HintMatcher.HintErrorConfig→FSharpLint.Framework.Ast.AstNodeFSharpLint.Rules.HintMatcher.HintMatcher→FSharpLint.Framework.Ast.AstNodeFSharpLint.Rules.HintMatcher.ToStringConfig→FSharpLint.Framework.Ast.AstNode
- Direction
- Rules.HintMatcher uses Framework.Ast, so a change to Framework.Ast can break Rules.HintMatcher, while a change to Rules.HintMatcher can't break Framework.Ast.
- Position
- Below the diagonal: Rules.HintMatcher uses a module listed above it, which is the healthy direction.
13→2 Rules.HintMatcher uses Framework.HintParserTypes✕
- Connections
- 5 pairs of types, where a type in Rules.HintMatcher uses a type in Framework.HintParserTypes.
- The types involved
FSharpLint.Rules.HintMatcher.HintErrorConfig→FSharpLint.Framework.HintParserTypes.HintFSharpLint.Rules.HintMatcher.HintMatcher→FSharpLint.Framework.HintParserTypes.ConstantFSharpLint.Rules.HintMatcher.HintMatcher→FSharpLint.Framework.HintParserTypes.HintNodeFSharpLint.Rules.HintMatcher.HintMatcher→FSharpLint.Framework.HintParserTypes.SuggestionFSharpLint.Rules.HintMatcher.ToStringConfig→FSharpLint.Framework.HintParserTypes.HintNode
- Direction
- Rules.HintMatcher uses Framework.HintParserTypes, so a change to Framework.HintParserTypes can break Rules.HintMatcher, while a change to Rules.HintMatcher can't break Framework.HintParserTypes.
- Position
- Below the diagonal: Rules.HintMatcher uses a module listed above it, which is the healthy direction.
13→3 Rules.HintMatcher uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.HintMatcher uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.HintMatcher.HintMatcher→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.HintMatcher uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.HintMatcher, while a change to Rules.HintMatcher can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.HintMatcher uses a module listed above it, which is the healthy direction.
13→6 Rules.HintMatcher uses Framework.MergeSyntaxTrees✕
- Connections
- 1 pair of types, where a type in Rules.HintMatcher uses a type in Framework.MergeSyntaxTrees.
- The types involved
FSharpLint.Rules.HintMatcher.Config→FSharpLint.Framework.MergeSyntaxTrees.Edges
- Direction
- Rules.HintMatcher uses Framework.MergeSyntaxTrees, so a change to Framework.MergeSyntaxTrees can break Rules.HintMatcher, while a change to Rules.HintMatcher can't break Framework.MergeSyntaxTrees.
- Position
- Below the diagonal: Rules.HintMatcher uses a module listed above it, which is the healthy direction.
13→8 Rules.HintMatcher uses Framework.Rules✕
- Connections
- 3 pairs of types, where a type in Rules.HintMatcher uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.HintMatcher.HintErrorConfig→FSharpLint.Framework.Rules.AstNodeRuleParamsFSharpLint.Rules.HintMatcher.HintMatcher→FSharpLint.Framework.Rules.RuleFSharpLint.Rules.HintMatcher.ToStringConfig→FSharpLint.Framework.Rules.AstNodeRuleParams
- Direction
- Rules.HintMatcher uses Framework.Rules, so a change to Framework.Rules can break Rules.HintMatcher, while a change to Rules.HintMatcher can't break Framework.Rules.
- Position
- Below the diagonal: Rules.HintMatcher uses a module listed above it, which is the healthy direction.
14→3 Rules.IndexerAccessorStyleConsistency uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.IndexerAccessorStyleConsistency uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.IndexerAccessorStyleConsistency.IndexerAccessorStyleConsistency→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.IndexerAccessorStyleConsistency uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.IndexerAccessorStyleConsistency, while a change to Rules.IndexerAccessorStyleConsistency can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.IndexerAccessorStyleConsistency uses a module listed above it, which is the healthy direction.
14→8 Rules.IndexerAccessorStyleConsistency uses Framework.Rules✕
- Connections
- 2 pairs of types, where a type in Rules.IndexerAccessorStyleConsistency uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.IndexerAccessorStyleConsistency.IndexerAccessorStyleConsistency→FSharpLint.Framework.Rules.AstNodeRuleParamsFSharpLint.Rules.IndexerAccessorStyleConsistency.IndexerAccessorStyleConsistency→FSharpLint.Framework.Rules.Rule
- Direction
- Rules.IndexerAccessorStyleConsistency uses Framework.Rules, so a change to Framework.Rules can break Rules.IndexerAccessorStyleConsistency, while a change to Rules.IndexerAccessorStyleConsistency can't break Framework.Rules.
- Position
- Below the diagonal: Rules.IndexerAccessorStyleConsistency uses a module listed above it, which is the healthy direction.
15→3 Rules.MaxCharactersOnLine uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.MaxCharactersOnLine uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.MaxCharactersOnLine.MaxCharactersOnLine→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.MaxCharactersOnLine uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.MaxCharactersOnLine, while a change to Rules.MaxCharactersOnLine can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.MaxCharactersOnLine uses a module listed above it, which is the healthy direction.
15→8 Rules.MaxCharactersOnLine uses Framework.Rules✕
- Connections
- 2 pairs of types, where a type in Rules.MaxCharactersOnLine uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.MaxCharactersOnLine.MaxCharactersOnLine→FSharpLint.Framework.Rules.LineRuleParamsFSharpLint.Rules.MaxCharactersOnLine.MaxCharactersOnLine→FSharpLint.Framework.Rules.Rule
- Direction
- Rules.MaxCharactersOnLine uses Framework.Rules, so a change to Framework.Rules can break Rules.MaxCharactersOnLine, while a change to Rules.MaxCharactersOnLine can't break Framework.Rules.
- Position
- Below the diagonal: Rules.MaxCharactersOnLine uses a module listed above it, which is the healthy direction.
16→3 Rules.MaxLinesInClass uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.MaxLinesInClass uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.MaxLinesInClass.MaxLinesInClass→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.MaxLinesInClass uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.MaxLinesInClass, while a change to Rules.MaxLinesInClass can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.MaxLinesInClass uses a module listed above it, which is the healthy direction.
16→7 Rules.MaxLinesInClass uses Rules.Helper.SourceLength✕
- Connections
- 1 pair of types, where a type in Rules.MaxLinesInClass uses a type in Rules.Helper.SourceLength.
- The types involved
FSharpLint.Rules.MaxLinesInClass.MaxLinesInClass→FSharpLint.Rules.Helper.SourceLength.Config
- Direction
- Rules.MaxLinesInClass uses Rules.Helper.SourceLength, so a change to Rules.Helper.SourceLength can break Rules.MaxLinesInClass, while a change to Rules.MaxLinesInClass can't break Rules.Helper.SourceLength.
- Position
- Below the diagonal: Rules.MaxLinesInClass uses a module listed above it, which is the healthy direction.
16→8 Rules.MaxLinesInClass uses Framework.Rules✕
- Connections
- 2 pairs of types, where a type in Rules.MaxLinesInClass uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.MaxLinesInClass.MaxLinesInClass→FSharpLint.Framework.Rules.AstNodeRuleParamsFSharpLint.Rules.MaxLinesInClass.MaxLinesInClass→FSharpLint.Framework.Rules.Rule
- Direction
- Rules.MaxLinesInClass uses Framework.Rules, so a change to Framework.Rules can break Rules.MaxLinesInClass, while a change to Rules.MaxLinesInClass can't break Framework.Rules.
- Position
- Below the diagonal: Rules.MaxLinesInClass uses a module listed above it, which is the healthy direction.
17→3 Rules.MaxLinesInConstructor uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.MaxLinesInConstructor uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.MaxLinesInConstructor.MaxLinesInConstructor→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.MaxLinesInConstructor uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.MaxLinesInConstructor, while a change to Rules.MaxLinesInConstructor can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.MaxLinesInConstructor uses a module listed above it, which is the healthy direction.
17→7 Rules.MaxLinesInConstructor uses Rules.Helper.SourceLength✕
- Connections
- 1 pair of types, where a type in Rules.MaxLinesInConstructor uses a type in Rules.Helper.SourceLength.
- The types involved
FSharpLint.Rules.MaxLinesInConstructor.MaxLinesInConstructor→FSharpLint.Rules.Helper.SourceLength.Config
- Direction
- Rules.MaxLinesInConstructor uses Rules.Helper.SourceLength, so a change to Rules.Helper.SourceLength can break Rules.MaxLinesInConstructor, while a change to Rules.MaxLinesInConstructor can't break Rules.Helper.SourceLength.
- Position
- Below the diagonal: Rules.MaxLinesInConstructor uses a module listed above it, which is the healthy direction.
17→8 Rules.MaxLinesInConstructor uses Framework.Rules✕
- Connections
- 2 pairs of types, where a type in Rules.MaxLinesInConstructor uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.MaxLinesInConstructor.MaxLinesInConstructor→FSharpLint.Framework.Rules.AstNodeRuleParamsFSharpLint.Rules.MaxLinesInConstructor.MaxLinesInConstructor→FSharpLint.Framework.Rules.Rule
- Direction
- Rules.MaxLinesInConstructor uses Framework.Rules, so a change to Framework.Rules can break Rules.MaxLinesInConstructor, while a change to Rules.MaxLinesInConstructor can't break Framework.Rules.
- Position
- Below the diagonal: Rules.MaxLinesInConstructor uses a module listed above it, which is the healthy direction.
18→3 Rules.MaxLinesInEnum uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.MaxLinesInEnum uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.MaxLinesInEnum.MaxLinesInEnum→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.MaxLinesInEnum uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.MaxLinesInEnum, while a change to Rules.MaxLinesInEnum can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.MaxLinesInEnum uses a module listed above it, which is the healthy direction.
18→7 Rules.MaxLinesInEnum uses Rules.Helper.SourceLength✕
- Connections
- 1 pair of types, where a type in Rules.MaxLinesInEnum uses a type in Rules.Helper.SourceLength.
- The types involved
FSharpLint.Rules.MaxLinesInEnum.MaxLinesInEnum→FSharpLint.Rules.Helper.SourceLength.Config
- Direction
- Rules.MaxLinesInEnum uses Rules.Helper.SourceLength, so a change to Rules.Helper.SourceLength can break Rules.MaxLinesInEnum, while a change to Rules.MaxLinesInEnum can't break Rules.Helper.SourceLength.
- Position
- Below the diagonal: Rules.MaxLinesInEnum uses a module listed above it, which is the healthy direction.
18→8 Rules.MaxLinesInEnum uses Framework.Rules✕
- Connections
- 2 pairs of types, where a type in Rules.MaxLinesInEnum uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.MaxLinesInEnum.MaxLinesInEnum→FSharpLint.Framework.Rules.AstNodeRuleParamsFSharpLint.Rules.MaxLinesInEnum.MaxLinesInEnum→FSharpLint.Framework.Rules.Rule
- Direction
- Rules.MaxLinesInEnum uses Framework.Rules, so a change to Framework.Rules can break Rules.MaxLinesInEnum, while a change to Rules.MaxLinesInEnum can't break Framework.Rules.
- Position
- Below the diagonal: Rules.MaxLinesInEnum uses a module listed above it, which is the healthy direction.
19→3 Rules.MaxLinesInFile uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.MaxLinesInFile uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.MaxLinesInFile.MaxLinesInFile→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.MaxLinesInFile uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.MaxLinesInFile, while a change to Rules.MaxLinesInFile can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.MaxLinesInFile uses a module listed above it, which is the healthy direction.
19→8 Rules.MaxLinesInFile uses Framework.Rules✕
- Connections
- 2 pairs of types, where a type in Rules.MaxLinesInFile uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.MaxLinesInFile.MaxLinesInFile→FSharpLint.Framework.Rules.LineRuleParamsFSharpLint.Rules.MaxLinesInFile.MaxLinesInFile→FSharpLint.Framework.Rules.Rule
- Direction
- Rules.MaxLinesInFile uses Framework.Rules, so a change to Framework.Rules can break Rules.MaxLinesInFile, while a change to Rules.MaxLinesInFile can't break Framework.Rules.
- Position
- Below the diagonal: Rules.MaxLinesInFile uses a module listed above it, which is the healthy direction.
20→3 Rules.MaxLinesInFunction uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.MaxLinesInFunction uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.MaxLinesInFunction.MaxLinesInFunction→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.MaxLinesInFunction uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.MaxLinesInFunction, while a change to Rules.MaxLinesInFunction can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.MaxLinesInFunction uses a module listed above it, which is the healthy direction.
20→7 Rules.MaxLinesInFunction uses Rules.Helper.SourceLength✕
- Connections
- 1 pair of types, where a type in Rules.MaxLinesInFunction uses a type in Rules.Helper.SourceLength.
- The types involved
FSharpLint.Rules.MaxLinesInFunction.MaxLinesInFunction→FSharpLint.Rules.Helper.SourceLength.Config
- Direction
- Rules.MaxLinesInFunction uses Rules.Helper.SourceLength, so a change to Rules.Helper.SourceLength can break Rules.MaxLinesInFunction, while a change to Rules.MaxLinesInFunction can't break Rules.Helper.SourceLength.
- Position
- Below the diagonal: Rules.MaxLinesInFunction uses a module listed above it, which is the healthy direction.
20→8 Rules.MaxLinesInFunction uses Framework.Rules✕
- Connections
- 2 pairs of types, where a type in Rules.MaxLinesInFunction uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.MaxLinesInFunction.MaxLinesInFunction→FSharpLint.Framework.Rules.AstNodeRuleParamsFSharpLint.Rules.MaxLinesInFunction.MaxLinesInFunction→FSharpLint.Framework.Rules.Rule
- Direction
- Rules.MaxLinesInFunction uses Framework.Rules, so a change to Framework.Rules can break Rules.MaxLinesInFunction, while a change to Rules.MaxLinesInFunction can't break Framework.Rules.
- Position
- Below the diagonal: Rules.MaxLinesInFunction uses a module listed above it, which is the healthy direction.
21→3 Rules.MaxLinesInLambdaFunction uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.MaxLinesInLambdaFunction uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.MaxLinesInLambdaFunction.MaxLinesInLambdaFunction→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.MaxLinesInLambdaFunction uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.MaxLinesInLambdaFunction, while a change to Rules.MaxLinesInLambdaFunction can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.MaxLinesInLambdaFunction uses a module listed above it, which is the healthy direction.
21→7 Rules.MaxLinesInLambdaFunction uses Rules.Helper.SourceLength✕
- Connections
- 1 pair of types, where a type in Rules.MaxLinesInLambdaFunction uses a type in Rules.Helper.SourceLength.
- The types involved
FSharpLint.Rules.MaxLinesInLambdaFunction.MaxLinesInLambdaFunction→FSharpLint.Rules.Helper.SourceLength.Config
- Direction
- Rules.MaxLinesInLambdaFunction uses Rules.Helper.SourceLength, so a change to Rules.Helper.SourceLength can break Rules.MaxLinesInLambdaFunction, while a change to Rules.MaxLinesInLambdaFunction can't break Rules.Helper.SourceLength.
- Position
- Below the diagonal: Rules.MaxLinesInLambdaFunction uses a module listed above it, which is the healthy direction.
21→8 Rules.MaxLinesInLambdaFunction uses Framework.Rules✕
- Connections
- 2 pairs of types, where a type in Rules.MaxLinesInLambdaFunction uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.MaxLinesInLambdaFunction.MaxLinesInLambdaFunction→FSharpLint.Framework.Rules.AstNodeRuleParamsFSharpLint.Rules.MaxLinesInLambdaFunction.MaxLinesInLambdaFunction→FSharpLint.Framework.Rules.Rule
- Direction
- Rules.MaxLinesInLambdaFunction uses Framework.Rules, so a change to Framework.Rules can break Rules.MaxLinesInLambdaFunction, while a change to Rules.MaxLinesInLambdaFunction can't break Framework.Rules.
- Position
- Below the diagonal: Rules.MaxLinesInLambdaFunction uses a module listed above it, which is the healthy direction.
22→3 Rules.MaxLinesInMatchLambdaFunction uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.MaxLinesInMatchLambdaFunction uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.MaxLinesInMatchLambdaFunction.MaxLinesInMatchLambdaFunction→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.MaxLinesInMatchLambdaFunction uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.MaxLinesInMatchLambdaFunction, while a change to Rules.MaxLinesInMatchLambdaFunction can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.MaxLinesInMatchLambdaFunction uses a module listed above it, which is the healthy direction.
22→7 Rules.MaxLinesInMatchLambdaFunction uses Rules.Helper.SourceLength✕
- Connections
- 1 pair of types, where a type in Rules.MaxLinesInMatchLambdaFunction uses a type in Rules.Helper.SourceLength.
- The types involved
FSharpLint.Rules.MaxLinesInMatchLambdaFunction.MaxLinesInMatchLambdaFunction→FSharpLint.Rules.Helper.SourceLength.Config
- Direction
- Rules.MaxLinesInMatchLambdaFunction uses Rules.Helper.SourceLength, so a change to Rules.Helper.SourceLength can break Rules.MaxLinesInMatchLambdaFunction, while a change to Rules.MaxLinesInMatchLambdaFunction can't break Rules.Helper.SourceLength.
- Position
- Below the diagonal: Rules.MaxLinesInMatchLambdaFunction uses a module listed above it, which is the healthy direction.
22→8 Rules.MaxLinesInMatchLambdaFunction uses Framework.Rules✕
- Connections
- 2 pairs of types, where a type in Rules.MaxLinesInMatchLambdaFunction uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.MaxLinesInMatchLambdaFunction.MaxLinesInMatchLambdaFunction→FSharpLint.Framework.Rules.AstNodeRuleParamsFSharpLint.Rules.MaxLinesInMatchLambdaFunction.MaxLinesInMatchLambdaFunction→FSharpLint.Framework.Rules.Rule
- Direction
- Rules.MaxLinesInMatchLambdaFunction uses Framework.Rules, so a change to Framework.Rules can break Rules.MaxLinesInMatchLambdaFunction, while a change to Rules.MaxLinesInMatchLambdaFunction can't break Framework.Rules.
- Position
- Below the diagonal: Rules.MaxLinesInMatchLambdaFunction uses a module listed above it, which is the healthy direction.
23→3 Rules.MaxLinesInMember uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.MaxLinesInMember uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.MaxLinesInMember.MaxLinesInMember→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.MaxLinesInMember uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.MaxLinesInMember, while a change to Rules.MaxLinesInMember can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.MaxLinesInMember uses a module listed above it, which is the healthy direction.
23→7 Rules.MaxLinesInMember uses Rules.Helper.SourceLength✕
- Connections
- 1 pair of types, where a type in Rules.MaxLinesInMember uses a type in Rules.Helper.SourceLength.
- The types involved
FSharpLint.Rules.MaxLinesInMember.MaxLinesInMember→FSharpLint.Rules.Helper.SourceLength.Config
- Direction
- Rules.MaxLinesInMember uses Rules.Helper.SourceLength, so a change to Rules.Helper.SourceLength can break Rules.MaxLinesInMember, while a change to Rules.MaxLinesInMember can't break Rules.Helper.SourceLength.
- Position
- Below the diagonal: Rules.MaxLinesInMember uses a module listed above it, which is the healthy direction.
23→8 Rules.MaxLinesInMember uses Framework.Rules✕
- Connections
- 2 pairs of types, where a type in Rules.MaxLinesInMember uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.MaxLinesInMember.MaxLinesInMember→FSharpLint.Framework.Rules.AstNodeRuleParamsFSharpLint.Rules.MaxLinesInMember.MaxLinesInMember→FSharpLint.Framework.Rules.Rule
- Direction
- Rules.MaxLinesInMember uses Framework.Rules, so a change to Framework.Rules can break Rules.MaxLinesInMember, while a change to Rules.MaxLinesInMember can't break Framework.Rules.
- Position
- Below the diagonal: Rules.MaxLinesInMember uses a module listed above it, which is the healthy direction.
24→3 Rules.MaxLinesInModule uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.MaxLinesInModule uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.MaxLinesInModule.MaxLinesInModule→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.MaxLinesInModule uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.MaxLinesInModule, while a change to Rules.MaxLinesInModule can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.MaxLinesInModule uses a module listed above it, which is the healthy direction.
24→7 Rules.MaxLinesInModule uses Rules.Helper.SourceLength✕
- Connections
- 1 pair of types, where a type in Rules.MaxLinesInModule uses a type in Rules.Helper.SourceLength.
- The types involved
FSharpLint.Rules.MaxLinesInModule.MaxLinesInModule→FSharpLint.Rules.Helper.SourceLength.Config
- Direction
- Rules.MaxLinesInModule uses Rules.Helper.SourceLength, so a change to Rules.Helper.SourceLength can break Rules.MaxLinesInModule, while a change to Rules.MaxLinesInModule can't break Rules.Helper.SourceLength.
- Position
- Below the diagonal: Rules.MaxLinesInModule uses a module listed above it, which is the healthy direction.
24→8 Rules.MaxLinesInModule uses Framework.Rules✕
- Connections
- 2 pairs of types, where a type in Rules.MaxLinesInModule uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.MaxLinesInModule.MaxLinesInModule→FSharpLint.Framework.Rules.AstNodeRuleParamsFSharpLint.Rules.MaxLinesInModule.MaxLinesInModule→FSharpLint.Framework.Rules.Rule
- Direction
- Rules.MaxLinesInModule uses Framework.Rules, so a change to Framework.Rules can break Rules.MaxLinesInModule, while a change to Rules.MaxLinesInModule can't break Framework.Rules.
- Position
- Below the diagonal: Rules.MaxLinesInModule uses a module listed above it, which is the healthy direction.
25→3 Rules.MaxLinesInProperty uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.MaxLinesInProperty uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.MaxLinesInProperty.MaxLinesInProperty→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.MaxLinesInProperty uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.MaxLinesInProperty, while a change to Rules.MaxLinesInProperty can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.MaxLinesInProperty uses a module listed above it, which is the healthy direction.
25→7 Rules.MaxLinesInProperty uses Rules.Helper.SourceLength✕
- Connections
- 1 pair of types, where a type in Rules.MaxLinesInProperty uses a type in Rules.Helper.SourceLength.
- The types involved
FSharpLint.Rules.MaxLinesInProperty.MaxLinesInProperty→FSharpLint.Rules.Helper.SourceLength.Config
- Direction
- Rules.MaxLinesInProperty uses Rules.Helper.SourceLength, so a change to Rules.Helper.SourceLength can break Rules.MaxLinesInProperty, while a change to Rules.MaxLinesInProperty can't break Rules.Helper.SourceLength.
- Position
- Below the diagonal: Rules.MaxLinesInProperty uses a module listed above it, which is the healthy direction.
25→8 Rules.MaxLinesInProperty uses Framework.Rules✕
- Connections
- 2 pairs of types, where a type in Rules.MaxLinesInProperty uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.MaxLinesInProperty.MaxLinesInProperty→FSharpLint.Framework.Rules.AstNodeRuleParamsFSharpLint.Rules.MaxLinesInProperty.MaxLinesInProperty→FSharpLint.Framework.Rules.Rule
- Direction
- Rules.MaxLinesInProperty uses Framework.Rules, so a change to Framework.Rules can break Rules.MaxLinesInProperty, while a change to Rules.MaxLinesInProperty can't break Framework.Rules.
- Position
- Below the diagonal: Rules.MaxLinesInProperty uses a module listed above it, which is the healthy direction.
26→3 Rules.MaxLinesInRecord uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.MaxLinesInRecord uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.MaxLinesInRecord.MaxLinesInRecord→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.MaxLinesInRecord uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.MaxLinesInRecord, while a change to Rules.MaxLinesInRecord can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.MaxLinesInRecord uses a module listed above it, which is the healthy direction.
26→7 Rules.MaxLinesInRecord uses Rules.Helper.SourceLength✕
- Connections
- 1 pair of types, where a type in Rules.MaxLinesInRecord uses a type in Rules.Helper.SourceLength.
- The types involved
FSharpLint.Rules.MaxLinesInRecord.MaxLinesInRecord→FSharpLint.Rules.Helper.SourceLength.Config
- Direction
- Rules.MaxLinesInRecord uses Rules.Helper.SourceLength, so a change to Rules.Helper.SourceLength can break Rules.MaxLinesInRecord, while a change to Rules.MaxLinesInRecord can't break Rules.Helper.SourceLength.
- Position
- Below the diagonal: Rules.MaxLinesInRecord uses a module listed above it, which is the healthy direction.
26→8 Rules.MaxLinesInRecord uses Framework.Rules✕
- Connections
- 2 pairs of types, where a type in Rules.MaxLinesInRecord uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.MaxLinesInRecord.MaxLinesInRecord→FSharpLint.Framework.Rules.AstNodeRuleParamsFSharpLint.Rules.MaxLinesInRecord.MaxLinesInRecord→FSharpLint.Framework.Rules.Rule
- Direction
- Rules.MaxLinesInRecord uses Framework.Rules, so a change to Framework.Rules can break Rules.MaxLinesInRecord, while a change to Rules.MaxLinesInRecord can't break Framework.Rules.
- Position
- Below the diagonal: Rules.MaxLinesInRecord uses a module listed above it, which is the healthy direction.
27→3 Rules.MaxLinesInUnion uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.MaxLinesInUnion uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.MaxLinesInUnion.MaxLinesInUnion→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.MaxLinesInUnion uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.MaxLinesInUnion, while a change to Rules.MaxLinesInUnion can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.MaxLinesInUnion uses a module listed above it, which is the healthy direction.
27→7 Rules.MaxLinesInUnion uses Rules.Helper.SourceLength✕
- Connections
- 1 pair of types, where a type in Rules.MaxLinesInUnion uses a type in Rules.Helper.SourceLength.
- The types involved
FSharpLint.Rules.MaxLinesInUnion.MaxLinesInUnion→FSharpLint.Rules.Helper.SourceLength.Config
- Direction
- Rules.MaxLinesInUnion uses Rules.Helper.SourceLength, so a change to Rules.Helper.SourceLength can break Rules.MaxLinesInUnion, while a change to Rules.MaxLinesInUnion can't break Rules.Helper.SourceLength.
- Position
- Below the diagonal: Rules.MaxLinesInUnion uses a module listed above it, which is the healthy direction.
27→8 Rules.MaxLinesInUnion uses Framework.Rules✕
- Connections
- 2 pairs of types, where a type in Rules.MaxLinesInUnion uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.MaxLinesInUnion.MaxLinesInUnion→FSharpLint.Framework.Rules.AstNodeRuleParamsFSharpLint.Rules.MaxLinesInUnion.MaxLinesInUnion→FSharpLint.Framework.Rules.Rule
- Direction
- Rules.MaxLinesInUnion uses Framework.Rules, so a change to Framework.Rules can break Rules.MaxLinesInUnion, while a change to Rules.MaxLinesInUnion can't break Framework.Rules.
- Position
- Below the diagonal: Rules.MaxLinesInUnion uses a module listed above it, which is the healthy direction.
28→3 Rules.MaxLinesInValue uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.MaxLinesInValue uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.MaxLinesInValue.MaxLinesInValue→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.MaxLinesInValue uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.MaxLinesInValue, while a change to Rules.MaxLinesInValue can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.MaxLinesInValue uses a module listed above it, which is the healthy direction.
28→7 Rules.MaxLinesInValue uses Rules.Helper.SourceLength✕
- Connections
- 1 pair of types, where a type in Rules.MaxLinesInValue uses a type in Rules.Helper.SourceLength.
- The types involved
FSharpLint.Rules.MaxLinesInValue.MaxLinesInValue→FSharpLint.Rules.Helper.SourceLength.Config
- Direction
- Rules.MaxLinesInValue uses Rules.Helper.SourceLength, so a change to Rules.Helper.SourceLength can break Rules.MaxLinesInValue, while a change to Rules.MaxLinesInValue can't break Rules.Helper.SourceLength.
- Position
- Below the diagonal: Rules.MaxLinesInValue uses a module listed above it, which is the healthy direction.
28→8 Rules.MaxLinesInValue uses Framework.Rules✕
- Connections
- 2 pairs of types, where a type in Rules.MaxLinesInValue uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.MaxLinesInValue.MaxLinesInValue→FSharpLint.Framework.Rules.AstNodeRuleParamsFSharpLint.Rules.MaxLinesInValue.MaxLinesInValue→FSharpLint.Framework.Rules.Rule
- Direction
- Rules.MaxLinesInValue uses Framework.Rules, so a change to Framework.Rules can break Rules.MaxLinesInValue, while a change to Rules.MaxLinesInValue can't break Framework.Rules.
- Position
- Below the diagonal: Rules.MaxLinesInValue uses a module listed above it, which is the healthy direction.
29→3 Rules.MaxNumberOfItemsInTuple uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.MaxNumberOfItemsInTuple uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.MaxNumberOfItemsInTuple.MaxNumberOfItemsInTuple→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.MaxNumberOfItemsInTuple uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.MaxNumberOfItemsInTuple, while a change to Rules.MaxNumberOfItemsInTuple can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.MaxNumberOfItemsInTuple uses a module listed above it, which is the healthy direction.
29→4 Rules.MaxNumberOfItemsInTuple uses Rules.Helper.NumberOfItems✕
- Connections
- 1 pair of types, where a type in Rules.MaxNumberOfItemsInTuple uses a type in Rules.Helper.NumberOfItems.
- The types involved
FSharpLint.Rules.MaxNumberOfItemsInTuple.MaxNumberOfItemsInTuple→FSharpLint.Rules.Helper.NumberOfItems.Config
- Direction
- Rules.MaxNumberOfItemsInTuple uses Rules.Helper.NumberOfItems, so a change to Rules.Helper.NumberOfItems can break Rules.MaxNumberOfItemsInTuple, while a change to Rules.MaxNumberOfItemsInTuple can't break Rules.Helper.NumberOfItems.
- Position
- Below the diagonal: Rules.MaxNumberOfItemsInTuple uses a module listed above it, which is the healthy direction.
29→5 Rules.MaxNumberOfItemsInTuple uses Framework.AbstractSyntaxArray✕
- Connections
- 1 pair of types, where a type in Rules.MaxNumberOfItemsInTuple uses a type in Framework.AbstractSyntaxArray.
- The types involved
FSharpLint.Rules.MaxNumberOfItemsInTuple.MaxNumberOfItemsInTuple→FSharpLint.Framework.AbstractSyntaxArray.Node
- Direction
- Rules.MaxNumberOfItemsInTuple uses Framework.AbstractSyntaxArray, so a change to Framework.AbstractSyntaxArray can break Rules.MaxNumberOfItemsInTuple, while a change to Rules.MaxNumberOfItemsInTuple can't break Framework.AbstractSyntaxArray.
- Position
- Below the diagonal: Rules.MaxNumberOfItemsInTuple uses a module listed above it, which is the healthy direction.
29→8 Rules.MaxNumberOfItemsInTuple uses Framework.Rules✕
- Connections
- 2 pairs of types, where a type in Rules.MaxNumberOfItemsInTuple uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.MaxNumberOfItemsInTuple.MaxNumberOfItemsInTuple→FSharpLint.Framework.Rules.AstNodeRuleParamsFSharpLint.Rules.MaxNumberOfItemsInTuple.MaxNumberOfItemsInTuple→FSharpLint.Framework.Rules.Rule
- Direction
- Rules.MaxNumberOfItemsInTuple uses Framework.Rules, so a change to Framework.Rules can break Rules.MaxNumberOfItemsInTuple, while a change to Rules.MaxNumberOfItemsInTuple can't break Framework.Rules.
- Position
- Below the diagonal: Rules.MaxNumberOfItemsInTuple uses a module listed above it, which is the healthy direction.
30→1 Rules.NestedStatements uses Framework.Ast✕
- Connections
- 1 pair of types, where a type in Rules.NestedStatements uses a type in Framework.Ast.
- The types involved
FSharpLint.Rules.NestedStatements.NestedStatements→FSharpLint.Framework.Ast.AstNode
- Direction
- Rules.NestedStatements uses Framework.Ast, so a change to Framework.Ast can break Rules.NestedStatements, while a change to Rules.NestedStatements can't break Framework.Ast.
- Position
- Below the diagonal: Rules.NestedStatements uses a module listed above it, which is the healthy direction.
30→3 Rules.NestedStatements uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.NestedStatements uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.NestedStatements.NestedStatements→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.NestedStatements uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.NestedStatements, while a change to Rules.NestedStatements can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.NestedStatements uses a module listed above it, which is the healthy direction.
30→8 Rules.NestedStatements uses Framework.Rules✕
- Connections
- 2 pairs of types, where a type in Rules.NestedStatements uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.NestedStatements.NestedStatements→FSharpLint.Framework.Rules.AstNodeRuleParamsFSharpLint.Rules.NestedStatements.NestedStatements→FSharpLint.Framework.Rules.Rule
- Direction
- Rules.NestedStatements uses Framework.Rules, so a change to Framework.Rules can break Rules.NestedStatements, while a change to Rules.NestedStatements can't break Framework.Rules.
- Position
- Below the diagonal: Rules.NestedStatements uses a module listed above it, which is the healthy direction.
31→1 Rules.NoAsyncRunSynchronouslyInLibrary uses Framework.Ast✕
- Connections
- 1 pair of types, where a type in Rules.NoAsyncRunSynchronouslyInLibrary uses a type in Framework.Ast.
- The types involved
FSharpLint.Rules.NoAsyncRunSynchronouslyInLibrary.NoAsyncRunSynchronouslyInLibrary→FSharpLint.Framework.Ast.AstNode
- Direction
- Rules.NoAsyncRunSynchronouslyInLibrary uses Framework.Ast, so a change to Framework.Ast can break Rules.NoAsyncRunSynchronouslyInLibrary, while a change to Rules.NoAsyncRunSynchronouslyInLibrary can't break Framework.Ast.
- Position
- Below the diagonal: Rules.NoAsyncRunSynchronouslyInLibrary uses a module listed above it, which is the healthy direction.
31→3 Rules.NoAsyncRunSynchronouslyInLibrary uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.NoAsyncRunSynchronouslyInLibrary uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.NoAsyncRunSynchronouslyInLibrary.NoAsyncRunSynchronouslyInLibrary→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.NoAsyncRunSynchronouslyInLibrary uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.NoAsyncRunSynchronouslyInLibrary, while a change to Rules.NoAsyncRunSynchronouslyInLibrary can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.NoAsyncRunSynchronouslyInLibrary uses a module listed above it, which is the healthy direction.
31→5 Rules.NoAsyncRunSynchronouslyInLibrary uses Framework.AbstractSyntaxArray✕
- Connections
- 1 pair of types, where a type in Rules.NoAsyncRunSynchronouslyInLibrary uses a type in Framework.AbstractSyntaxArray.
- The types involved
FSharpLint.Rules.NoAsyncRunSynchronouslyInLibrary.NoAsyncRunSynchronouslyInLibrary→FSharpLint.Framework.AbstractSyntaxArray.Node
- Direction
- Rules.NoAsyncRunSynchronouslyInLibrary uses Framework.AbstractSyntaxArray, so a change to Framework.AbstractSyntaxArray can break Rules.NoAsyncRunSynchronouslyInLibrary, while a change to Rules.NoAsyncRunSynchronouslyInLibrary can't break Framework.AbstractSyntaxArray.
- Position
- Below the diagonal: Rules.NoAsyncRunSynchronouslyInLibrary uses a module listed above it, which is the healthy direction.
31→8 Rules.NoAsyncRunSynchronouslyInLibrary uses Framework.Rules✕
- Connections
- 2 pairs of types, where a type in Rules.NoAsyncRunSynchronouslyInLibrary uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.NoAsyncRunSynchronouslyInLibrary.NoAsyncRunSynchronouslyInLibrary→FSharpLint.Framework.Rules.AstNodeRuleParamsFSharpLint.Rules.NoAsyncRunSynchronouslyInLibrary.NoAsyncRunSynchronouslyInLibrary→FSharpLint.Framework.Rules.Rule
- Direction
- Rules.NoAsyncRunSynchronouslyInLibrary uses Framework.Rules, so a change to Framework.Rules can break Rules.NoAsyncRunSynchronouslyInLibrary, while a change to Rules.NoAsyncRunSynchronouslyInLibrary can't break Framework.Rules.
- Position
- Below the diagonal: Rules.NoAsyncRunSynchronouslyInLibrary uses a module listed above it, which is the healthy direction.
32→3 Rules.PatternMatchClauseIndentation uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.PatternMatchClauseIndentation uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.PatternMatchClauseIndentation.PatternMatchClauseIndentation→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.PatternMatchClauseIndentation uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.PatternMatchClauseIndentation, while a change to Rules.PatternMatchClauseIndentation can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.PatternMatchClauseIndentation uses a module listed above it, which is the healthy direction.
32→8 Rules.PatternMatchClauseIndentation uses Framework.Rules✕
- Connections
- 2 pairs of types, where a type in Rules.PatternMatchClauseIndentation uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.PatternMatchClauseIndentation.PatternMatchClauseIndentation→FSharpLint.Framework.Rules.AstNodeRuleParamsFSharpLint.Rules.PatternMatchClauseIndentation.PatternMatchClauseIndentation→FSharpLint.Framework.Rules.Rule
- Direction
- Rules.PatternMatchClauseIndentation uses Framework.Rules, so a change to Framework.Rules can break Rules.PatternMatchClauseIndentation, while a change to Rules.PatternMatchClauseIndentation can't break Framework.Rules.
- Position
- Below the diagonal: Rules.PatternMatchClauseIndentation uses a module listed above it, which is the healthy direction.
33→1 Rules.RecursiveAsyncFunction uses Framework.Ast✕
- Connections
- 1 pair of types, where a type in Rules.RecursiveAsyncFunction uses a type in Framework.Ast.
- The types involved
FSharpLint.Rules.RecursiveAsyncFunction.RecursiveAsyncFunction→FSharpLint.Framework.Ast.AstNode
- Direction
- Rules.RecursiveAsyncFunction uses Framework.Ast, so a change to Framework.Ast can break Rules.RecursiveAsyncFunction, while a change to Rules.RecursiveAsyncFunction can't break Framework.Ast.
- Position
- Below the diagonal: Rules.RecursiveAsyncFunction uses a module listed above it, which is the healthy direction.
33→3 Rules.RecursiveAsyncFunction uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.RecursiveAsyncFunction uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.RecursiveAsyncFunction.RecursiveAsyncFunction→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.RecursiveAsyncFunction uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.RecursiveAsyncFunction, while a change to Rules.RecursiveAsyncFunction can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.RecursiveAsyncFunction uses a module listed above it, which is the healthy direction.
33→8 Rules.RecursiveAsyncFunction uses Framework.Rules✕
- Connections
- 2 pairs of types, where a type in Rules.RecursiveAsyncFunction uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.RecursiveAsyncFunction.RecursiveAsyncFunction→FSharpLint.Framework.Rules.AstNodeRuleParamsFSharpLint.Rules.RecursiveAsyncFunction.RecursiveAsyncFunction→FSharpLint.Framework.Rules.Rule
- Direction
- Rules.RecursiveAsyncFunction uses Framework.Rules, so a change to Framework.Rules can break Rules.RecursiveAsyncFunction, while a change to Rules.RecursiveAsyncFunction can't break Framework.Rules.
- Position
- Below the diagonal: Rules.RecursiveAsyncFunction uses a module listed above it, which is the healthy direction.
34→3 Rules.SimpleAsyncComplementaryHelpers uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.SimpleAsyncComplementaryHelpers uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.SimpleAsyncComplementaryHelpers.SimpleAsyncComplementaryHelpers→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.SimpleAsyncComplementaryHelpers uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.SimpleAsyncComplementaryHelpers, while a change to Rules.SimpleAsyncComplementaryHelpers can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.SimpleAsyncComplementaryHelpers uses a module listed above it, which is the healthy direction.
34→8 Rules.SimpleAsyncComplementaryHelpers uses Framework.Rules✕
- Connections
- 2 pairs of types, where a type in Rules.SimpleAsyncComplementaryHelpers uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.SimpleAsyncComplementaryHelpers.SimpleAsyncComplementaryHelpers→FSharpLint.Framework.Rules.AstNodeRuleParamsFSharpLint.Rules.SimpleAsyncComplementaryHelpers.SimpleAsyncComplementaryHelpers→FSharpLint.Framework.Rules.Rule
- Direction
- Rules.SimpleAsyncComplementaryHelpers uses Framework.Rules, so a change to Framework.Rules can break Rules.SimpleAsyncComplementaryHelpers, while a change to Rules.SimpleAsyncComplementaryHelpers can't break Framework.Rules.
- Position
- Below the diagonal: Rules.SimpleAsyncComplementaryHelpers uses a module listed above it, which is the healthy direction.
35→3 Rules.TrailingWhitespaceOnLine uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.TrailingWhitespaceOnLine uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.TrailingWhitespaceOnLine.TrailingWhitespaceOnLine→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.TrailingWhitespaceOnLine uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.TrailingWhitespaceOnLine, while a change to Rules.TrailingWhitespaceOnLine can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.TrailingWhitespaceOnLine uses a module listed above it, which is the healthy direction.
35→8 Rules.TrailingWhitespaceOnLine uses Framework.Rules✕
- Connections
- 2 pairs of types, where a type in Rules.TrailingWhitespaceOnLine uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.TrailingWhitespaceOnLine.TrailingWhitespaceOnLine→FSharpLint.Framework.Rules.LineRuleParamsFSharpLint.Rules.TrailingWhitespaceOnLine.TrailingWhitespaceOnLine→FSharpLint.Framework.Rules.Rule
- Direction
- Rules.TrailingWhitespaceOnLine uses Framework.Rules, so a change to Framework.Rules can break Rules.TrailingWhitespaceOnLine, while a change to Rules.TrailingWhitespaceOnLine can't break Framework.Rules.
- Position
- Below the diagonal: Rules.TrailingWhitespaceOnLine uses a module listed above it, which is the healthy direction.
36→1 Rules.TupleParentheses uses Framework.Ast✕
- Connections
- 1 pair of types, where a type in Rules.TupleParentheses uses a type in Framework.Ast.
- The types involved
FSharpLint.Rules.TupleParentheses.TupleParentheses→FSharpLint.Framework.Ast.AstNode
- Direction
- Rules.TupleParentheses uses Framework.Ast, so a change to Framework.Ast can break Rules.TupleParentheses, while a change to Rules.TupleParentheses can't break Framework.Ast.
- Position
- Below the diagonal: Rules.TupleParentheses uses a module listed above it, which is the healthy direction.
36→3 Rules.TupleParentheses uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.TupleParentheses uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.TupleParentheses.TupleParentheses→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.TupleParentheses uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.TupleParentheses, while a change to Rules.TupleParentheses can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.TupleParentheses uses a module listed above it, which is the healthy direction.
36→8 Rules.TupleParentheses uses Framework.Rules✕
- Connections
- 2 pairs of types, where a type in Rules.TupleParentheses uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.TupleParentheses.TupleParentheses→FSharpLint.Framework.Rules.AstNodeRuleParamsFSharpLint.Rules.TupleParentheses.TupleParentheses→FSharpLint.Framework.Rules.Rule
- Direction
- Rules.TupleParentheses uses Framework.Rules, so a change to Framework.Rules can break Rules.TupleParentheses, while a change to Rules.TupleParentheses can't break Framework.Rules.
- Position
- Below the diagonal: Rules.TupleParentheses uses a module listed above it, which is the healthy direction.
37→3 Rules.TypePrefixing uses Framework.Suggestion✕
- Connections
- 1 pair of types, where a type in Rules.TypePrefixing uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Rules.TypePrefixing.TypePrefixing→FSharpLint.Framework.Suggestion.WarningDetails
- Direction
- Rules.TypePrefixing uses Framework.Suggestion, so a change to Framework.Suggestion can break Rules.TypePrefixing, while a change to Rules.TypePrefixing can't break Framework.Suggestion.
- Position
- Below the diagonal: Rules.TypePrefixing uses a module listed above it, which is the healthy direction.
37→8 Rules.TypePrefixing uses Framework.Rules✕
- Connections
- 3 pairs of types, where a type in Rules.TypePrefixing uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.TypePrefixing.CheckTypePrefixingConfig→FSharpLint.Framework.Rules.AstNodeRuleParamsFSharpLint.Rules.TypePrefixing.TypePrefixing→FSharpLint.Framework.Rules.AstNodeRuleParamsFSharpLint.Rules.TypePrefixing.TypePrefixing→FSharpLint.Framework.Rules.Rule
- Direction
- Rules.TypePrefixing uses Framework.Rules, so a change to Framework.Rules can break Rules.TypePrefixing, while a change to Rules.TypePrefixing can't break Framework.Rules.
- Position
- Below the diagonal: Rules.TypePrefixing uses a module listed above it, which is the healthy direction.
38→4 Framework.Configuration uses Rules.Helper.NumberOfItems✕
- Connections
- 1 pair of types, where a type in Framework.Configuration uses a type in Rules.Helper.NumberOfItems.
- The types involved
FSharpLint.Framework.Configuration.NumberOfItemsConfig→FSharpLint.Rules.Helper.NumberOfItems.Config
- Direction
- Framework.Configuration uses Rules.Helper.NumberOfItems, so a change to Rules.Helper.NumberOfItems can break Framework.Configuration, while a change to Framework.Configuration can't break Rules.Helper.NumberOfItems.
- Position
- Below the diagonal: Framework.Configuration uses a module listed above it, which is the healthy direction.
38→7 Framework.Configuration uses Rules.Helper.SourceLength✕
- Connections
- 1 pair of types, where a type in Framework.Configuration uses a type in Rules.Helper.SourceLength.
- The types involved
FSharpLint.Framework.Configuration.SourceLengthConfig→FSharpLint.Rules.Helper.SourceLength.Config
- Direction
- Framework.Configuration uses Rules.Helper.SourceLength, so a change to Rules.Helper.SourceLength can break Framework.Configuration, while a change to Framework.Configuration can't break Rules.Helper.SourceLength.
- Position
- Below the diagonal: Framework.Configuration uses a module listed above it, which is the healthy direction.
38→8 Framework.Configuration uses Framework.Rules✕
- Connections
- 20 pairs of types, where a type in Framework.Configuration uses a type in Framework.Rules.
- The types involved
FSharpLint.Framework.Configuration.BindingConfig→FSharpLint.Framework.Rules.RuleFSharpLint.Framework.Configuration.Configuration→FSharpLint.Framework.Rules.GlobalRuleConfigFSharpLint.Framework.Configuration.Configuration→FSharpLint.Framework.Rules.RuleFSharpLint.Framework.Configuration.ConventionsConfig→FSharpLint.Framework.Rules.RuleFSharpLint.Framework.Configuration.FormattingConfig→FSharpLint.Framework.Rules.RuleFSharpLint.Framework.Configuration.LineRules→FSharpLint.Framework.Rules.LineRuleConfigFSharpLint.Framework.Configuration.LineRules→FSharpLint.Framework.Rules.LineRuleConfigWithContext`1FSharpLint.Framework.Configuration.LineRules→FSharpLint.Framework.Rules.RuleMetadata`1FSharpLint.Framework.Configuration.LoadedRules→FSharpLint.Framework.Rules.AstNodeRuleConfigFSharpLint.Framework.Configuration.LoadedRules→FSharpLint.Framework.Rules.GlobalRuleConfigFSharpLint.Framework.Configuration.LoadedRules→FSharpLint.Framework.Rules.RuleFSharpLint.Framework.Configuration.LoadedRules→FSharpLint.Framework.Rules.RuleMetadata`1FSharpLint.Framework.Configuration.NamesConfig→FSharpLint.Framework.Rules.NamingConfigFSharpLint.Framework.Configuration.NamesConfig→FSharpLint.Framework.Rules.RuleFSharpLint.Framework.Configuration.NumberOfItemsConfig→FSharpLint.Framework.Rules.RuleFSharpLint.Framework.Configuration.PatternMatchFormattingConfig→FSharpLint.Framework.Rules.RuleFSharpLint.Framework.Configuration.RaiseWithTooManyArgsConfig→FSharpLint.Framework.Rules.RuleFSharpLint.Framework.Configuration.SourceLengthConfig→FSharpLint.Framework.Rules.RuleFSharpLint.Framework.Configuration.TupleFormattingConfig→FSharpLint.Framework.Rules.RuleFSharpLint.Framework.Configuration.TypographyConfig→FSharpLint.Framework.Rules.Rule
- Direction
- Framework.Configuration uses Framework.Rules, so a change to Framework.Rules can break Framework.Configuration, while a change to Framework.Configuration can't break Framework.Rules.
- Position
- Below the diagonal: Framework.Configuration uses a module listed above it, which is the healthy direction.
38→11 Framework.Configuration uses Rules.CyclomaticComplexity✕
- Connections
- 1 pair of types, where a type in Framework.Configuration uses a type in Rules.CyclomaticComplexity.
- The types involved
FSharpLint.Framework.Configuration.ConventionsConfig→FSharpLint.Rules.CyclomaticComplexity.Config
- Direction
- Framework.Configuration uses Rules.CyclomaticComplexity, so a change to Rules.CyclomaticComplexity can break Framework.Configuration, while a change to Framework.Configuration can't break Rules.CyclomaticComplexity.
- Position
- Below the diagonal: Framework.Configuration uses a module listed above it, which is the healthy direction.
38→12 Framework.Configuration uses Rules.FavourConsistentThis✕
- Connections
- 1 pair of types, where a type in Framework.Configuration uses a type in Rules.FavourConsistentThis.
- The types involved
FSharpLint.Framework.Configuration.ConventionsConfig→FSharpLint.Rules.FavourConsistentThis.Config
- Direction
- Framework.Configuration uses Rules.FavourConsistentThis, so a change to Rules.FavourConsistentThis can break Framework.Configuration, while a change to Framework.Configuration can't break Rules.FavourConsistentThis.
- Position
- Below the diagonal: Framework.Configuration uses a module listed above it, which is the healthy direction.
38→14 Framework.Configuration uses Rules.IndexerAccessorStyleConsistency✕
- Connections
- 1 pair of types, where a type in Framework.Configuration uses a type in Rules.IndexerAccessorStyleConsistency.
- The types involved
FSharpLint.Framework.Configuration.ConventionsConfig→FSharpLint.Rules.IndexerAccessorStyleConsistency.Config
- Direction
- Framework.Configuration uses Rules.IndexerAccessorStyleConsistency, so a change to Rules.IndexerAccessorStyleConsistency can break Framework.Configuration, while a change to Framework.Configuration can't break Rules.IndexerAccessorStyleConsistency.
- Position
- Below the diagonal: Framework.Configuration uses a module listed above it, which is the healthy direction.
38→15 Framework.Configuration uses Rules.MaxCharactersOnLine✕
- Connections
- 1 pair of types, where a type in Framework.Configuration uses a type in Rules.MaxCharactersOnLine.
- The types involved
FSharpLint.Framework.Configuration.TypographyConfig→FSharpLint.Rules.MaxCharactersOnLine.Config
- Direction
- Framework.Configuration uses Rules.MaxCharactersOnLine, so a change to Rules.MaxCharactersOnLine can break Framework.Configuration, while a change to Framework.Configuration can't break Rules.MaxCharactersOnLine.
- Position
- Below the diagonal: Framework.Configuration uses a module listed above it, which is the healthy direction.
38→19 Framework.Configuration uses Rules.MaxLinesInFile✕
- Connections
- 1 pair of types, where a type in Framework.Configuration uses a type in Rules.MaxLinesInFile.
- The types involved
FSharpLint.Framework.Configuration.TypographyConfig→FSharpLint.Rules.MaxLinesInFile.Config
- Direction
- Framework.Configuration uses Rules.MaxLinesInFile, so a change to Rules.MaxLinesInFile can break Framework.Configuration, while a change to Framework.Configuration can't break Rules.MaxLinesInFile.
- Position
- Below the diagonal: Framework.Configuration uses a module listed above it, which is the healthy direction.
38→30 Framework.Configuration uses Rules.NestedStatements✕
- Connections
- 1 pair of types, where a type in Framework.Configuration uses a type in Rules.NestedStatements.
- The types involved
FSharpLint.Framework.Configuration.ConventionsConfig→FSharpLint.Rules.NestedStatements.Config
- Direction
- Framework.Configuration uses Rules.NestedStatements, so a change to Rules.NestedStatements can break Framework.Configuration, while a change to Framework.Configuration can't break Rules.NestedStatements.
- Position
- Below the diagonal: Framework.Configuration uses a module listed above it, which is the healthy direction.
38→32 Framework.Configuration uses Rules.PatternMatchClauseIndentation✕
- Connections
- 1 pair of types, where a type in Framework.Configuration uses a type in Rules.PatternMatchClauseIndentation.
- The types involved
FSharpLint.Framework.Configuration.PatternMatchFormattingConfig→FSharpLint.Rules.PatternMatchClauseIndentation.Config
- Direction
- Framework.Configuration uses Rules.PatternMatchClauseIndentation, so a change to Rules.PatternMatchClauseIndentation can break Framework.Configuration, while a change to Framework.Configuration can't break Rules.PatternMatchClauseIndentation.
- Position
- Below the diagonal: Framework.Configuration uses a module listed above it, which is the healthy direction.
38→35 Framework.Configuration uses Rules.TrailingWhitespaceOnLine✕
- Connections
- 1 pair of types, where a type in Framework.Configuration uses a type in Rules.TrailingWhitespaceOnLine.
- The types involved
FSharpLint.Framework.Configuration.TypographyConfig→FSharpLint.Rules.TrailingWhitespaceOnLine.Config
- Direction
- Framework.Configuration uses Rules.TrailingWhitespaceOnLine, so a change to Rules.TrailingWhitespaceOnLine can break Framework.Configuration, while a change to Framework.Configuration can't break Rules.TrailingWhitespaceOnLine.
- Position
- Below the diagonal: Framework.Configuration uses a module listed above it, which is the healthy direction.
38→37 Framework.Configuration uses Rules.TypePrefixing✕
- Connections
- 2 pairs of types, where a type in Framework.Configuration uses a type in Rules.TypePrefixing.
- The types involved
FSharpLint.Framework.Configuration.Configuration→FSharpLint.Rules.TypePrefixing.ConfigFSharpLint.Framework.Configuration.FormattingConfig→FSharpLint.Rules.TypePrefixing.Config
- Direction
- Framework.Configuration uses Rules.TypePrefixing, so a change to Rules.TypePrefixing can break Framework.Configuration, while a change to Framework.Configuration can't break Rules.TypePrefixing.
- Position
- Below the diagonal: Framework.Configuration uses a module listed above it, which is the healthy direction.
39→1 Rules.HintMatcher.FormatHint uses Framework.Ast✕
- Connections
- 1 pair of types, where a type in Rules.HintMatcher.FormatHint uses a type in Framework.Ast.
- The types involved
FSharpLint.Rules.HintMatcher.FormatHint.FormatHint→FSharpLint.Framework.Ast.AstNode
- Direction
- Rules.HintMatcher.FormatHint uses Framework.Ast, so a change to Framework.Ast can break Rules.HintMatcher.FormatHint, while a change to Rules.HintMatcher.FormatHint can't break Framework.Ast.
- Position
- Below the diagonal: Rules.HintMatcher.FormatHint uses a module listed above it, which is the healthy direction.
39→2 Rules.HintMatcher.FormatHint uses Framework.HintParserTypes✕
- Connections
- 3 pairs of types, where a type in Rules.HintMatcher.FormatHint uses a type in Framework.HintParserTypes.
- The types involved
FSharpLint.Rules.HintMatcher.FormatHint.FormatHint→FSharpLint.Framework.HintParserTypes.ConstantFSharpLint.Rules.HintMatcher.FormatHint.FormatHint→FSharpLint.Framework.HintParserTypes.ExpressionFSharpLint.Rules.HintMatcher.FormatHint.FormatHint→FSharpLint.Framework.HintParserTypes.LambdaArg
- Direction
- Rules.HintMatcher.FormatHint uses Framework.HintParserTypes, so a change to Framework.HintParserTypes can break Rules.HintMatcher.FormatHint, while a change to Rules.HintMatcher.FormatHint can't break Framework.HintParserTypes.
- Position
- Below the diagonal: Rules.HintMatcher.FormatHint uses a module listed above it, which is the healthy direction.
39→8 Rules.HintMatcher.FormatHint uses Framework.Rules✕
- Connections
- 1 pair of types, where a type in Rules.HintMatcher.FormatHint uses a type in Framework.Rules.
- The types involved
FSharpLint.Rules.HintMatcher.FormatHint.FormatHint→FSharpLint.Framework.Rules.AstNodeRuleParams
- Direction
- Rules.HintMatcher.FormatHint uses Framework.Rules, so a change to Framework.Rules can break Rules.HintMatcher.FormatHint, while a change to Rules.HintMatcher.FormatHint can't break Framework.Rules.
- Position
- Below the diagonal: Rules.HintMatcher.FormatHint uses a module listed above it, which is the healthy direction.
39→13 Rules.HintMatcher.FormatHint uses Rules.HintMatcher✕
- Connections
- 1 pair of types, where a type in Rules.HintMatcher.FormatHint uses a type in Rules.HintMatcher.
- The types involved
FSharpLint.Rules.HintMatcher.FormatHint.FormatHint→FSharpLint.Rules.HintMatcher.ToStringConfig
- Direction
- Rules.HintMatcher.FormatHint uses Rules.HintMatcher, so a change to Rules.HintMatcher can break Rules.HintMatcher.FormatHint, while a change to Rules.HintMatcher.FormatHint can't break Rules.HintMatcher.
- Position
- Below the diagonal: Rules.HintMatcher.FormatHint uses a module listed above it, which is the healthy direction.
40→3 Application.Lint uses Framework.Suggestion✕
- Connections
- 3 pairs of types, where a type in Application.Lint uses a type in Framework.Suggestion.
- The types involved
FSharpLint.Application.Lint.Lint→FSharpLint.Framework.Suggestion.LintWarningFSharpLint.Application.Lint.LintResult→FSharpLint.Framework.Suggestion.LintWarningFSharpLint.Application.Lint.ProjectProgress→FSharpLint.Framework.Suggestion.LintWarning
- Direction
- Application.Lint uses Framework.Suggestion, so a change to Framework.Suggestion can break Application.Lint, while a change to Application.Lint can't break Framework.Suggestion.
- Position
- Below the diagonal: Application.Lint uses a module listed above it, which is the healthy direction.
40→5 Application.Lint uses Framework.AbstractSyntaxArray✕
- Connections
- 1 pair of types, where a type in Application.Lint uses a type in Framework.AbstractSyntaxArray.
- The types involved
FSharpLint.Application.Lint.RunAstNodeRulesConfig→FSharpLint.Framework.AbstractSyntaxArray.Node
- Direction
- Application.Lint uses Framework.AbstractSyntaxArray, so a change to Framework.AbstractSyntaxArray can break Application.Lint, while a change to Application.Lint can't break Framework.AbstractSyntaxArray.
- Position
- Below the diagonal: Application.Lint uses a module listed above it, which is the healthy direction.
40→8 Application.Lint uses Framework.Rules✕
- Connections
- 4 pairs of types, where a type in Application.Lint uses a type in Framework.Rules.
- The types involved
FSharpLint.Application.Lint.RunAstNodeRulesConfig→FSharpLint.Framework.Rules.AstNodeRuleConfigFSharpLint.Application.Lint.RunAstNodeRulesConfig→FSharpLint.Framework.Rules.GlobalRuleConfigFSharpLint.Application.Lint.RunAstNodeRulesConfig→FSharpLint.Framework.Rules.RuleMetadata`1FSharpLint.Application.Lint.RunLineRulesConfig→FSharpLint.Framework.Rules.GlobalRuleConfig
- Direction
- Application.Lint uses Framework.Rules, so a change to Framework.Rules can break Application.Lint, while a change to Application.Lint can't break Framework.Rules.
- Position
- Below the diagonal: Application.Lint uses a module listed above it, which is the healthy direction.
40→38 Application.Lint uses Framework.Configuration✕
- Connections
- 3 pairs of types, where a type in Application.Lint uses a type in Framework.Configuration.
- The types involved
FSharpLint.Application.Lint.ConfigurationParam→FSharpLint.Framework.Configuration.ConfigurationFSharpLint.Application.Lint.Lint→FSharpLint.Framework.Configuration.ConfigurationFSharpLint.Application.Lint.RunLineRulesConfig→FSharpLint.Framework.Configuration.LineRules
- Direction
- Application.Lint uses Framework.Configuration, so a change to Framework.Configuration can break Application.Lint, while a change to Application.Lint can't break Framework.Configuration.
- Position
- Below the diagonal: Application.Lint uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 20 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 3 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with FSharpLint.Console.fsproj; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with FSharpLint.Console.fsproj. | +4.8 pts | Low | ADR Quality |
| Resolve the 1 Outdated finding(s) in Dependency Hygiene — start with Directory.Packages.props. | +3.9 pts | Low | Dependency Hygiene |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +6.5 pts | Medium | Observability |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +4.2 pts | Medium | Architecture documentation |
| Resolve the 9 Orphaned file finding(s) in Knowledge Freshness — start with Indentation.fs, XmlDocumentation.fs, NestedStatements.fs. | +1.2 pts | Low | Knowledge Freshness |
| Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with FSharpLint.FunctionalTest.TestedProject.NetCore.fsproj. | +1.1 pts | Low | Platform End-of-Life |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +1.0 pts | Low | Bus Factor |
| 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. | +1.7 pts | Medium | Documentation (README) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| src/FSharpLint.Core/Rules/Hints/HintMatcher.fs | 7.0 | Near-clean | Cyclomatic Complexity: FormatHint.toString (cyclomatic 33) |
| src/FSharpLint.Core/Rules/Conventions/CyclomaticComplexity.fs | 7.2 | Near-clean | Cyclomatic Complexity: CyclomaticComplexity.runner (cyclomatic 18) |
| src/FSharpLint.Core/Application/Lint.fs | 7.2 | Near-clean | Cognitive Complexity: Lint.asyncLintSolution (cognitive 18) |
| src/FSharpLint.Core/Rules/Conventions/Naming/InternalValuesNames.fs | 7.2 | Near-clean | Code Duplication: Duplicated block (17 lines × 2) |
| REDACTED | 7.2 | Near-clean | Secrets (history): High secret: REDACTED |
| src/FSharpLint.Console/Program.fs | 7.4 | Near-clean | Cyclomatic Complexity: Program.main (cyclomatic 37) |
| src/FSharpLint.Core/Rules/Conventions/Naming/AvoidTooShortNames.fs | 7.4 | Near-clean | Cyclomatic Complexity: AvoidTooShortNames.runner (cyclomatic 23) |
| src/FSharpLint.Core/Framework/HintParserUtilities.fs | 7.4 | Near-clean | Cyclomatic Complexity: MergeSyntaxTrees.getEdgesRec (cyclomatic 21) |
| src/FSharpLint.Core/Rules/Conventions/FailwithBadUsage.fs | 7.4 | Near-clean | Cyclomatic Complexity: FailwithBadUsage.checkExpr (cyclomatic 20) |
| src/FSharpLint.Core/Rules/Conventions/Naming/PrivateValuesNames.fs | 7.4 | Near-clean | Cognitive Complexity: PrivateValuesNames.rule (cognitive 17) |
| src/FSharpLint.Core/Rules/Conventions/Naming/SimpleAsyncComplementaryHelpers.fs | 7.8 | Near-clean | Cyclomatic Complexity: SimpleAsyncComplementaryHelpers.runner (cyclomatic 38) |
| src/FSharpLint.Core/Rules/Conventions/Naming/AsynchronousFunctionNames.fs | 7.8 | Near-clean | Cyclomatic Complexity: AsynchronousFunctionNames.runner (cyclomatic 25) |
| src/FSharpLint.Core/Rules/Conventions/NoPartialFunctions.fs | 7.8 | Near-clean | Cyclomatic Complexity: NoPartialFunctions.runner (cyclomatic 22) |
| src/FSharpLint.Core/Rules/Conventions/DisallowShadowing.fs | 7.8 | Near-clean | Cyclomatic Complexity: DisallowShadowing.runner (cyclomatic 21) |
| src/FSharpLint.Core/Rules/NamingHelper.fs | 7.8 | Near-clean | Cyclomatic Complexity: Naming.toAstNodeRule (cyclomatic 20) |
| src/FSharpLint.Core/Rules/Conventions/NoMutatorFunctions.fs | 7.8 | Near-clean | Cyclomatic Complexity: NoMutatorFunctions.runner (cyclomatic 19) |
| src/FSharpLint.Core/Rules/Conventions/FavourNestedFunctions.fs | 7.8 | Near-clean | Cyclomatic Complexity: FavourNestedFunctions.runner (cyclomatic 17) |
| src/FSharpLint.Core/Rules/Conventions/AvoidSinglePipeOperator.fs | 7.8 | Near-clean | Cognitive Complexity: AvoidSinglePipeOperator.checkExprContinuationPassingStyle (cognitive 36) |
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 38 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 38 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, 120 of 144 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
- D8 Code Coverage — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
- D11 Test Reliability — 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. Test reliability is scored on the 1 tier(s) that produced comparable repeat runs; 1 tier(s) did not, and are excluded from the measurement rather than counted (unit: measured (0 flaky); other: not included — too large to re-run within its budget). This is OUR limitation, not a defect in the repository.
- 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/FSharpLint.Core/Rules/Conventions/NoMutatorFunctions.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.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
- 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.
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.
- 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.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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
15 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SimpleAsyncComplementaryHelpers.runner at 38. A further 15 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 NoPartialFunctions.tryFindTypedExpression at 44 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/FSharpLint.Core/Framework/AbstractSyntaxArray.fs (AbstractSyntaxArray.astNodeToSyntaxNode at 34), src/FSharpLint.Core/Rules/Conventions/FavourStaticEmptyFields.fs (FavourStaticEmptyFields.processExpressions at 21), src/FSharpLint.Core/Rules/Smells/AsyncExceptionWithoutReturn.fs (AsyncExceptionWithoutReturn.checkExpression at 20). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 15 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with SimpleAsyncComplementaryHelpers.runner (cyclomatic 38), Program.main (cyclomatic 37), FormatHint.toString (cyclomatic 33). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 15 together lifts Cyclomatic Complexity from 7.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
28 method(s) exceeded the cognitive complexity threshold of 15; the worst was AsynchronousFunctionNames.runner at 44.
What to do
- Bring the 5 bodies over 30 down to 30 or less in Cognitive Complexity — start with AsynchronousFunctionNames.runner (cognitive 44), SimpleAsyncComplementaryHelpers.runner (cognitive 42), NoPartialFunctions.runner (cognitive 41). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cognitive Complexity from 5.4 to about 6.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
4 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 4 FileTooLong finding(s) in God Classes — start with Configuration.fs, HintMatcher.fs, HintParser.fs. — One of this dimension's main actionable groups (4 warning-level).
D4 · Code Duplication
23 duplicated block group(s) detected. A further 10 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 4 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with AvoidSinglePipeOperator.fs, FailwithBadUsage.fs, AvoidTooShortNames.fs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with GenericTypesNames.fs, MaxLinesInClass.fs, MaxLinesInConstructor.fs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with ModuleNames.fs, ClassMemberSpacing.fs, HintMatcher.fs. — One of this dimension's main actionable groups (3 warning-level).
D5 · Coupling
8 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 3 classes have LCOM4 above 3.
D11 · Test Reliability
Only 1 of 2 test tiers measured — the score covers those alone. 0 flaky across 1 measured tier(s). unit: measured (0 flaky); other: not included — too large to re-run within its budget.
D12 · Dependency Hygiene
17 outdated, 0 vulnerable, 0 deprecated packages.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 173 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 21 direct `PackageReference`(s), and 152 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/FSharpLint.Core/Rules/Conventions/NoMutatorFunctions.fs (5×19=95)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with NoMutatorFunctions.fs. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
7 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/FSharpLint.Core/Framework/HintParserUtilities.fs. Counted over 57 of the 127 production source files in this repository: 69 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with FSharpLint.Console.fsproj. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 2 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
86 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
20 finding(s): 0 critical, 19 high, 1 medium, 0 low. 14 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 14 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 (14 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
3 finding(s): 0 critical, 2 high, 1 medium, 0 low.
What to do
- Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
9 of 58 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/FSharpLint.Core/Rules/Formatting/Typography/Indentation.fs. Counted over 58 of the 127 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 9 Orphaned file finding(s) in Knowledge Freshness — start with Indentation.fs, XmlDocumentation.fs, NestedStatements.fs. — One of this dimension's main actionable groups (9 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 8 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
What to do
- Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with FSharpLint.FunctionalTest.TestedProject.NetCore.fsproj. — One of this dimension's main actionable groups (1 warning-level).
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
P1 · CI/CD gates
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
- `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:7
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 77% | Checked 4 of 11 | Solid. |
| Architecture | 91% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 57% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 48% | Adequate — gated by P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 63% | Checked 4 of 10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 94% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
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 — 74 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. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- 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 — ~24205 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.
- 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.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; F#, JavaScript not measured.
- 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
- D8 Code Coverage — Coverage not measured — no coverage collector is wired up
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 36 value object(s); 1 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
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
- P8 Schema migrations — 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 not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- 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.
- 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
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — 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 — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 22 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 86 finding(s)
- FileTooLong: Application/Configuration.fs src/FSharpLint.Core/Application/Configuration.fs
- FileTooLong: Hints/HintMatcher.fs src/FSharpLint.Core/Rules/Hints/HintMatcher.fs
- FileTooLong: Framework/HintParser.fs src/FSharpLint.Core/Framework/HintParser.fs
- FileTooLong: Application/Lint.fs src/FSharpLint.Core/Application/Lint.fs
- Duplicated block (8 lines × 2) src/FSharpLint.Core/Rules/Conventions/AvoidSinglePipeOperator.fs:67
- Duplicated block (8 lines × 2) src/FSharpLint.Core/Rules/Conventions/FailwithBadUsage.fs:117
- Duplicated block (8 lines × 2) src/FSharpLint.Core/Rules/Conventions/Naming/AvoidTooShortNames.fs:97
- Duplicated block (8 lines × 2) src/FSharpLint.Core/Rules/Conventions/Naming/InternalValuesNames.fs:33
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/FSharpLint.Core/Rules/Conventions/Naming/GenericTypesNames.fs:1
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/FSharpLint.Core/Rules/Conventions/SourceLength/MaxLinesInClass.fs:1
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/FSharpLint.Core/Rules/Conventions/SourceLength/MaxLinesInConstructor.fs:1
- Duplicated block (9 lines × 2) src/FSharpLint.Core/Rules/Conventions/Naming/ModuleNames.fs:3
- Duplicated block (9 lines × 2) src/FSharpLint.Core/Rules/Formatting/Spacing/ClassMemberSpacing.fs:19
- Duplicated block (9 lines × 2) src/FSharpLint.Core/Rules/Hints/HintMatcher.fs:391
- Duplicated block (9 lines × 4) src/FSharpLint.Core/Rules/Conventions/Naming/GenericTypesNames.fs:3
- Duplicated block (9 lines × 4) src/FSharpLint.Core/Rules/Conventions/SourceLength/MaxLinesInConstructor.fs:3
- Duplicated block (6 lines × 2) src/FSharpLint.Core/Rules/Conventions/CyclomaticComplexity.fs:104
- Duplicated block (6 lines × 2) src/FSharpLint.Core/Rules/Conventions/CyclomaticComplexity.fs:113
- SimpleAsyncComplementaryHelpers.runner (cyclomatic 38) src/FSharpLint.Core/Rules/Conventions/Naming/SimpleAsyncComplementaryHelpers.fs:47
- Program.main (cyclomatic 37) src/FSharpLint.Console/Program.fs:116
- FormatHint.toString (cyclomatic 33) src/FSharpLint.Core/Rules/Hints/HintMatcher.fs:564
- Ast.expressionChildren (cyclomatic 31) src/FSharpLint.Core/Framework/Ast.fs:263
- AsynchronousFunctionNames.runner (cyclomatic 25) src/FSharpLint.Core/Rules/Conventions/Naming/AsynchronousFunctionNames.fs:18
- AvoidTooShortNames.runner (cyclomatic 23) src/FSharpLint.Core/Rules/Conventions/Naming/AvoidTooShortNames.fs:38
- NoPartialFunctions.runner (cyclomatic 22) src/FSharpLint.Core/Rules/Conventions/NoPartialFunctions.fs:289
- MergeSyntaxTrees.getEdgesRec (cyclomatic 21) src/FSharpLint.Core/Framework/HintParserUtilities.fs:298
- HintMatcher.rule (cyclomatic 21) src/FSharpLint.Core/Rules/Hints/HintMatcher.fs:689
- DisallowShadowing.runner (cyclomatic 21) src/FSharpLint.Core/Rules/Conventions/DisallowShadowing.fs:70
- Naming.toAstNodeRule (cyclomatic 20) src/FSharpLint.Core/Rules/NamingHelper.fs:117
- FailwithBadUsage.checkExpr (cyclomatic 20) src/FSharpLint.Core/Rules/Conventions/FailwithBadUsage.fs:27
- NoMutatorFunctions.runner (cyclomatic 19) src/FSharpLint.Core/Rules/Conventions/NoMutatorFunctions.fs:44
- CyclomaticComplexity.runner (cyclomatic 18) src/FSharpLint.Core/Rules/Conventions/CyclomaticComplexity.fs:136
- FavourNestedFunctions.runner (cyclomatic 17) src/FSharpLint.Core/Rules/Conventions/FavourNestedFunctions.fs:45
- Hotspot: src/FSharpLint.Core/Rules/Conventions/NoMutatorFunctions.fs src/FSharpLint.Core/Rules/Conventions/NoMutatorFunctions.fs:44
- AsynchronousFunctionNames.runner (cognitive 44) src/FSharpLint.Core/Rules/Conventions/Naming/AsynchronousFunctionNames.fs:18
- SimpleAsyncComplementaryHelpers.runner (cognitive 42) src/FSharpLint.Core/Rules/Conventions/Naming/SimpleAsyncComplementaryHelpers.fs:47
- NoPartialFunctions.runner (cognitive 41) src/FSharpLint.Core/Rules/Conventions/NoPartialFunctions.fs:289
- Program.main (cognitive 40) src/FSharpLint.Console/Program.fs:116
- AvoidSinglePipeOperator.checkExprContinuationPassingStyle (cognitive 36) src/FSharpLint.Core/Rules/Conventions/AvoidSinglePipeOperator.fs:39
- NoMutatorFunctions.runner (cognitive 28) src/FSharpLint.Core/Rules/Conventions/NoMutatorFunctions.fs:44
- AvoidTooShortNames.runner (cognitive 27) src/FSharpLint.Core/Rules/Conventions/Naming/AvoidTooShortNames.fs:38
- FavourNestedFunctions.runner (cognitive 25) src/FSharpLint.Core/Rules/Conventions/FavourNestedFunctions.fs:45
- FavourSingleton.runner (cognitive 25) src/FSharpLint.Core/Rules/Conventions/FavourSingleton.fs:11
- DisallowShadowing.runner (cognitive 24) src/FSharpLint.Core/Rules/Conventions/DisallowShadowing.fs:70
- HintMatcher.rule (cognitive 23) src/FSharpLint.Core/Rules/Hints/HintMatcher.fs:689
- MatchExpression.matchLambda (cognitive 23) src/FSharpLint.Core/Rules/Hints/HintMatcher.fs:311
- FailwithBadUsage.checkExpr (cognitive 21) src/FSharpLint.Core/Rules/Conventions/FailwithBadUsage.fs:27
- TypeNames.rule (cognitive 20) src/FSharpLint.Core/Rules/Conventions/Naming/TypeNames.fs:8
- InterfaceNames.rule (cognitive 20) src/FSharpLint.Core/Rules/Conventions/Naming/InterfaceNames.fs:8
- DiscourageStringInterpolationWithStringFormat.runner (cognitive 20) src/FSharpLint.Core/Rules/Conventions/DiscourageStringInterpolationWithStringFormat.fs:10
- Naming.toAstNodeRule (cognitive 19) src/FSharpLint.Core/Rules/NamingHelper.fs:117
- MeasureTypeNames.rule (cognitive 19) src/FSharpLint.Core/Rules/Conventions/Naming/MeasureTypeNames.fs:8
- SynchronousFunctionNames.runner (cognitive 19) src/FSharpLint.Core/Rules/Conventions/Naming/SynchronousFunctionNames.fs:12
- Lint.asyncLintSolution (cognitive 18) src/FSharpLint.Core/Application/Lint.fs:501
- MergeSyntaxTrees.getEdgesRec (cognitive 18) src/FSharpLint.Core/Framework/HintParserUtilities.fs:298
- MatchExpression.notPropertyInitialisationOrNamedParameter (cognitive 17) src/FSharpLint.Core/Rules/Hints/HintMatcher.fs:188
- PrivateValuesNames.rule (cognitive 17) src/FSharpLint.Core/Rules/Conventions/Naming/PrivateValuesNames.fs:9
- TypePrefixing.checkTypePrefixing (cognitive 17) src/FSharpLint.Core/Rules/Conventions/TypePrefixing.fs:29
- Program.inferFileType (cognitive 16) src/FSharpLint.Console/Program.fs:99
- Hints.checkTrie (cognitive 16) src/FSharpLint.Core/Rules/Hints/HintsHelper.fs:24
- PublicValuesNames.rule (cognitive 16) src/FSharpLint.Core/Rules/Conventions/Naming/PublicValuesNames.fs:9
- CyclomaticComplexity.runner (cognitive 16) src/FSharpLint.Core/Rules/Conventions/CyclomaticComplexity.fs:136
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (53 corresponding lines) src/FSharpLint.Core/Rules/Conventions/Naming/PrivateValuesNames.fs:1
- Edited copy of a member (57 corresponding lines) src/FSharpLint.Core/Rules/Formatting/Spacing/ClassMemberSpacing.fs:1
- Edited copy of a member (39 corresponding lines) src/FSharpLint.Core/Rules/Formatting/PatternMatchFormatting/PatternMatchClausesOnNewLine.fs:1
- Edited copy of a member (29 corresponding lines) src/FSharpLint.Core/Rules/Conventions/Naming/NestedFunctionNames.fs:1
- Edited copy of a member (24 corresponding lines) src/FSharpLint.Core/Rules/Conventions/Naming/ModuleNames.fs:1
- Edited copies of one member (3 members, 19+ corresponding lines) src/FSharpLint.Core/Rules/Conventions/Naming/EnumCasesNames.fs:1
- Edited copies of one member (3 members, 21+ corresponding lines) src/FSharpLint.Core/Rules/Conventions/SourceLength/MaxLinesInLambdaFunction.fs:1
- Duplicated block (21–25 lines × 2) src/FSharpLint.Core/Application/Lint.fs:38
- Duplicated block (19–20 lines × 2) src/FSharpLint.Core/Application/Lint.fs:565
- Duplicated block (19 lines × 2) src/FSharpLint.Core/Framework/AbstractSyntaxArray.fs:30
- Duplicated block (17 lines × 2) src/FSharpLint.Core/Rules/Conventions/Naming/InternalValuesNames.fs:7
- Duplicated block (16 lines × 3) src/FSharpLint.Core/Rules/Conventions/Naming/InterfaceNames.fs:5
- Duplicated block (13 lines × 3) src/FSharpLint.Core/Rules/Conventions/Naming/InternalValuesNames.fs:3
- Duplicated block (11 lines × 2) src/FSharpLint.Core/Rules/Conventions/Naming/NestedFunctionNames.fs:3
- Duplicated block (9–10 lines × 2) src/FSharpLint.Core/Rules/Conventions/Naming/PrivateValuesNames.fs:25
- Duplicated block (8 lines × 4) src/FSharpLint.Core/Rules/Conventions/SourceLength/MaxLinesInClass.fs:3
- Duplicated block (5 lines × 2) src/FSharpLint.Core/Framework/HintParserUtilities.fs:358
- Duplicated block (13 lines × 2) src/FSharpLint.Core/Rules/Conventions/NumberOfItems/MaxNumberOfItemsInTuple.fs:27
- Duplicated block (10 lines × 2) src/FSharpLint.Core/Rules/Conventions/Naming/InternalValuesNames.fs:34
- End-of-life runtime: .NET netcoreapp3.1 tests/FSharpLint.FunctionalTest.TestedProject/FSharpLint.FunctionalTest.TestedProject.NetCore/FSharpLint.FunctionalTest.TestedProject.NetCore.fsproj:4
- No structured logging
Minor — 20 finding(s)
- Orphaned file src/FSharpLint.Core/Rules/Formatting/Typography/Indentation.fs:1
- Orphaned file src/FSharpLint.Core/Rules/XmlDocumentation.fs:1
- Orphaned file src/FSharpLint.Core/Rules/Conventions/NestedStatements.fs:1
- Orphaned file src/FSharpLint.Core/Framework/AstInfo.fs:1
- Orphaned file src/FSharpLint.Core/Framework/Suppression.fs:1
- Orphaned file src/FSharpLint.Core/Rules/Formatting/PatternMatchFormatting/PatternMatchClauseIndentation.fs:1
- Orphaned file src/FSharpLint.Core/Rules/Conventions/RecursiveAsyncFunction.fs:1
- Orphaned file src/FSharpLint.Core/Rules/Formatting/UnionDefinitionIndentation.fs:1
- Orphaned file src/FSharpLint.Core/Rules/Formatting/Typography/TrailingWhitespaceOnLine.fs:1
- Outdated: Microsoft.SourceLink.GitHub Directory.Packages.props:24
- Off-boarding risk: anonymized user #1
- No ADRs found src/FSharpLint.Console/FSharpLint.Console.fsproj:5
- Projects may be oversized for their cohesion
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:4
- No dependency-update automation Directory.Packages.props:7
Minor — 16 finding(s)
- Outdated: FSharp.Core
- Outdated: FSharp.Compiler.Service
- Outdated: Ionide.ProjInfo
- Outdated: Ionide.ProjInfo.FCS
- Outdated: Ionide.ProjInfo.ProjectSystem
- Outdated: Microsoft.Build
- Outdated: Microsoft.Build.Framework
- Outdated: Microsoft.Build.Locator
- Outdated: Microsoft.Build.Tasks.Core
- Outdated: Microsoft.Build.Utilities.Core
- Outdated: BenchmarkDotNet
- Outdated: BenchmarkDotNet.Diagnostics.Windows
- Outdated: System.Reactive
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: NUnit
- Outdated: NUnit3TestAdapter
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-a123f8661bb042708dbb6f6043f4587f/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-a123f8661bb042708dbb6f6043f4587f/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 docs/static . | 20 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list FSharpLint.slnx package --vulnerable --include-transitive --format json | 3 | 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-c35e89ecaab94148af053737530dde30 | 0 | artifacts/raw/osv-scanner.json |