Executive summary
iwillspeak/feersum meets our standard for a template or a sample. It scores 61 out of 100 and is rated Strong, and 19 of its 20 critical findings are security problems in the build pipeline and in its automatic dependency updates.
Every lens scores high enough to be rated Strong, so no single lens holds the score back. The best first step is bringing the documentation in line with the code, worth about 4 points. Recording more design decisions comes next, worth about 3 points.
Sixteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two secrets can leak from the build pipeline, and one automatic update takes new releases before a bad one can be spotted. Pinning each tool to an exact version, limiting each secret to its own step and setting a waiting period for automatic updates would close these risks. The set of compiler warnings switched off in a project needs turning back on in the build file.
The product code is 7,365 lines, about €10,000 to rebuild.
Every lens already scores high enough to be rated Strong, so no single lens holds the score back.
Fixed since the last survey: 5 findings
- Code Duplication · Duplicated block (13–15 lines × 2) src/Serehfa/Booleans.cs
- Code Duplication · Duplicated block (15 lines × 2) src/Serehfa/ByteVectors.cs
- Code Duplication · Duplicated block (5 lines × 2) src/Serehfa/ArgHelpers.cs
- Dependency Hygiene · Vulnerable: MessagePack
- Dependency Hygiene · Deprecated: ReadLine.Reboot
Rebuild cost: about €10,000 · Estimate
| Cost to rebuild | €3,400 to €17,000, for 56 to 179 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Low, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 61. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 7,365 lines of product code |
| Comment lines | The estimate prices 7,253 lines. Comment lines count towards the size of 7,365 lines but aren't priced as work. |
| 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 CompilerServices | 2 CompilerServices.Binding.Binderctx | 3 CompilerServices.Binding.Environments | 4 CompilerServices.Binding.Ident | 5 CompilerServices.Compile.BuiltinMacros | 6 CompilerServices.Compile.Builtins | 7 CompilerServices.Compile.ExternUtils | 8 CompilerServices.Compile.Instrumentation | 9 CompilerServices.Compile.MonoHelpers | 10 CompilerServices.Diagnostics.Diagnostics | 11 CompilerServices.Eval | 12 CompilerServices.Text | 13 CompilerServices.Utils.Result | 14 LanguageServer | 15 CompilerServices.Diagnostics | 16 CompilerServices.Runtime | 17 CompilerServices.Syntax.Parse | 18 CompilerServices.Syntax.Tree | 19 CompilerServices.Text.SourceRegistry | 20 LanguageServer.Workspace | 21 CompilerServices.Binding | 22 CompilerServices.Binding.Stx | 23 CompilerServices.Compile | 24 CompilerServices.Syntax.Factories | 25 CompilerServices.Syntax.Factories.Convenience | 26 CompilerServices.Syntax.Tree.Patterns | 27 CompilerServices.Syntax.Tree.SyntaxUtils | 28 CompilerServices.Syntax.Tree.Utils | 29 CompilerServices.Binding.Binder | 30 CompilerServices.Binding.FrameCtx | 31 CompilerServices.Binding.Impl | 32 CompilerServices.Binding.Libraries | 33 CompilerServices.Binding.Lower | 34 CompilerServices.Binding.MacroParse | 35 CompilerServices.Binding.Macros | 36 CompilerServices.Binding.ResolutionEnv | 37 CompilerServices.Binding.Utils | 38 CompilerServices.Compile.Compilation | 39 CompilerServices.Compile.Emit | 40 CompilerServices.Compile.Utils |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 CompilerServices | ||||||||||||||||||||||||||||||||||||||||
| 2 CompilerServices.Binding.Binderctx | ||||||||||||||||||||||||||||||||||||||||
| 3 CompilerServices.Binding.Environments | ||||||||||||||||||||||||||||||||||||||||
| 4 CompilerServices.Binding.Ident | ||||||||||||||||||||||||||||||||||||||||
| 5 CompilerServices.Compile.BuiltinMacros | ||||||||||||||||||||||||||||||||||||||||
| 6 CompilerServices.Compile.Builtins | ||||||||||||||||||||||||||||||||||||||||
| 7 CompilerServices.Compile.ExternUtils | ||||||||||||||||||||||||||||||||||||||||
| 8 CompilerServices.Compile.Instrumentation | ||||||||||||||||||||||||||||||||||||||||
| 9 CompilerServices.Compile.MonoHelpers | ||||||||||||||||||||||||||||||||||||||||
| 10 CompilerServices.Diagnostics.Diagnostics | ||||||||||||||||||||||||||||||||||||||||
| 11 CompilerServices.Eval | ||||||||||||||||||||||||||||||||||||||||
| 12 CompilerServices.Text | ||||||||||||||||||||||||||||||||||||||||
| 13 CompilerServices.Utils.Result | ||||||||||||||||||||||||||||||||||||||||
| 14 LanguageServer | ||||||||||||||||||||||||||||||||||||||||
| 15 CompilerServices.Diagnostics | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 CompilerServices.Runtime | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 CompilerServices.Syntax.Parse | 3 | |||||||||||||||||||||||||||||||||||||||
| 18 CompilerServices.Syntax.Tree | 19 | |||||||||||||||||||||||||||||||||||||||
| 19 CompilerServices.Text.SourceRegistry | 2 | |||||||||||||||||||||||||||||||||||||||
| 20 LanguageServer.Workspace | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 CompilerServices.Binding | 5 | 2 | ||||||||||||||||||||||||||||||||||||||
| 22 CompilerServices.Binding.Stx | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 CompilerServices.Compile | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 CompilerServices.Syntax.Factories | 3 | |||||||||||||||||||||||||||||||||||||||
| 25 CompilerServices.Syntax.Factories.Convenience | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 CompilerServices.Syntax.Tree.Patterns | 2 | |||||||||||||||||||||||||||||||||||||||
| 27 CompilerServices.Syntax.Tree.SyntaxUtils | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 CompilerServices.Syntax.Tree.Utils | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 CompilerServices.Binding.Binder | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 30 CompilerServices.Binding.FrameCtx | 3 | |||||||||||||||||||||||||||||||||||||||
| 31 CompilerServices.Binding.Impl | 1 | 12 | ||||||||||||||||||||||||||||||||||||||
| 32 CompilerServices.Binding.Libraries | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 CompilerServices.Binding.Lower | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 CompilerServices.Binding.MacroParse | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 35 CompilerServices.Binding.Macros | 1 | 1 | 6 | |||||||||||||||||||||||||||||||||||||
| 36 CompilerServices.Binding.ResolutionEnv | 2 | |||||||||||||||||||||||||||||||||||||||
| 37 CompilerServices.Binding.Utils | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||||||
| 38 CompilerServices.Compile.Compilation | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 CompilerServices.Compile.Emit | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 CompilerServices.Compile.Utils | 3 | 2 |
15→12 CompilerServices.Diagnostics uses CompilerServices.Text✕
- Connections
- 1 pair of types, where a type in CompilerServices.Diagnostics uses a type in CompilerServices.Text.
- The types involved
Feersum.CompilerServices.Diagnostics.Diagnostic→Feersum.CompilerServices.Text.TextLocation
- Direction
- CompilerServices.Diagnostics uses CompilerServices.Text, so a change to CompilerServices.Text can break CompilerServices.Diagnostics, while a change to CompilerServices.Diagnostics can't break CompilerServices.Text.
- Position
- Below the diagonal: CompilerServices.Diagnostics uses a module listed above it, which is the healthy direction.
16→1 CompilerServices.Runtime uses CompilerServices✕
- Connections
- 1 pair of types, where a type in CompilerServices.Runtime uses a type in CompilerServices.
- The types involved
Feersum.CompilerServices.Runtime.Runtime→Feersum.CompilerServices.CompilationOptions
- Direction
- CompilerServices.Runtime uses CompilerServices, so a change to CompilerServices can break CompilerServices.Runtime, while a change to CompilerServices.Runtime can't break CompilerServices.
- Position
- Below the diagonal: CompilerServices.Runtime uses a module listed above it, which is the healthy direction.
17→12 CompilerServices.Syntax.Parse uses CompilerServices.Text✕
- Connections
- 3 pairs of types, where a type in CompilerServices.Syntax.Parse uses a type in CompilerServices.Text.
- The types involved
Feersum.CompilerServices.Syntax.Parse.Parse→Feersum.CompilerServices.Text.DocIdFeersum.CompilerServices.Syntax.Parse.Parse→Feersum.CompilerServices.Text.SourceRegistryFeersum.CompilerServices.Syntax.Parse.ParserState→Feersum.CompilerServices.Text.TextDocument
- Direction
- CompilerServices.Syntax.Parse uses CompilerServices.Text, so a change to CompilerServices.Text can break CompilerServices.Syntax.Parse, while a change to CompilerServices.Syntax.Parse can't break CompilerServices.Text.
- Position
- Below the diagonal: CompilerServices.Syntax.Parse uses a module listed above it, which is the healthy direction.
18→12 CompilerServices.Syntax.Tree uses CompilerServices.Text✕
- Connections
- 19 pairs of types, where a type in CompilerServices.Syntax.Tree uses a type in CompilerServices.Text.
- The types involved
Feersum.CompilerServices.Syntax.Tree.AstItem→Feersum.CompilerServices.Text.DocIdFeersum.CompilerServices.Syntax.Tree.AstNode→Feersum.CompilerServices.Text.DocIdFeersum.CompilerServices.Syntax.Tree.AstToken→Feersum.CompilerServices.Text.DocIdFeersum.CompilerServices.Syntax.Tree.BoolVal→Feersum.CompilerServices.Text.DocIdFeersum.CompilerServices.Syntax.Tree.ByteValue→Feersum.CompilerServices.Text.DocIdFeersum.CompilerServices.Syntax.Tree.ByteVec→Feersum.CompilerServices.Text.DocIdFeersum.CompilerServices.Syntax.Tree.CharVal→Feersum.CompilerServices.Text.DocIdFeersum.CompilerServices.Syntax.Tree.Constant→Feersum.CompilerServices.Text.DocIdFeersum.CompilerServices.Syntax.Tree.ConstantValue→Feersum.CompilerServices.Text.DocIdFeersum.CompilerServices.Syntax.Tree.DottedTail→Feersum.CompilerServices.Text.DocIdFeersum.CompilerServices.Syntax.Tree.Expression→Feersum.CompilerServices.Text.DocIdFeersum.CompilerServices.Syntax.Tree.Form→Feersum.CompilerServices.Text.DocIdFeersum.CompilerServices.Syntax.Tree.NumVal→Feersum.CompilerServices.Text.DocIdFeersum.CompilerServices.Syntax.Tree.Program→Feersum.CompilerServices.Text.DocIdFeersum.CompilerServices.Syntax.Tree.Quoted→Feersum.CompilerServices.Text.DocIdFeersum.CompilerServices.Syntax.Tree.ScriptProgram→Feersum.CompilerServices.Text.DocIdFeersum.CompilerServices.Syntax.Tree.StrVal→Feersum.CompilerServices.Text.DocIdFeersum.CompilerServices.Syntax.Tree.Symbol→Feersum.CompilerServices.Text.DocIdFeersum.CompilerServices.Syntax.Tree.Vec→Feersum.CompilerServices.Text.DocId
- Direction
- CompilerServices.Syntax.Tree uses CompilerServices.Text, so a change to CompilerServices.Text can break CompilerServices.Syntax.Tree, while a change to CompilerServices.Syntax.Tree can't break CompilerServices.Text.
- Position
- Below the diagonal: CompilerServices.Syntax.Tree uses a module listed above it, which is the healthy direction.
19→12 CompilerServices.Text.SourceRegistry uses CompilerServices.Text✕
- Connections
- 2 pairs of types, where a type in CompilerServices.Text.SourceRegistry uses a type in CompilerServices.Text.
- The types involved
Feersum.CompilerServices.Text.SourceRegistry.SourceRegistry→Feersum.CompilerServices.Text.DocIdFeersum.CompilerServices.Text.SourceRegistry.SourceRegistry→Feersum.CompilerServices.Text.TextLocation
- Direction
- CompilerServices.Text.SourceRegistry uses CompilerServices.Text, so a change to CompilerServices.Text can break CompilerServices.Text.SourceRegistry, while a change to CompilerServices.Text.SourceRegistry can't break CompilerServices.Text.
- Position
- Below the diagonal: CompilerServices.Text.SourceRegistry uses a module listed above it, which is the healthy direction.
20→14 LanguageServer.Workspace uses LanguageServer✕
- Connections
- 1 pair of types, where a type in LanguageServer.Workspace uses a type in LanguageServer.
- The types involved
Feersum.LanguageServer.Workspace.Workspace→Feersum.LanguageServer.WorkspaceMessage
- Direction
- LanguageServer.Workspace uses LanguageServer, so a change to LanguageServer can break LanguageServer.Workspace, while a change to LanguageServer.Workspace can't break LanguageServer.
- Position
- Below the diagonal: LanguageServer.Workspace uses a module listed above it, which is the healthy direction.
21→12 CompilerServices.Binding uses CompilerServices.Text✕
- Connections
- 5 pairs of types, where a type in CompilerServices.Binding uses a type in CompilerServices.Text.
- The types involved
Feersum.CompilerServices.Binding.BinderCtx→Feersum.CompilerServices.Text.SourceRegistryFeersum.CompilerServices.Binding.BoundExpr→Feersum.CompilerServices.Text.TextLocationFeersum.CompilerServices.Binding.Macro→Feersum.CompilerServices.Text.TextLocationFeersum.CompilerServices.Binding.MacroTemplate→Feersum.CompilerServices.Text.TextLocationFeersum.CompilerServices.Binding.Stx→Feersum.CompilerServices.Text.TextLocation
- Direction
- CompilerServices.Binding uses CompilerServices.Text, so a change to CompilerServices.Text can break CompilerServices.Binding, while a change to CompilerServices.Binding can't break CompilerServices.Text.
- Position
- Below the diagonal: CompilerServices.Binding uses a module listed above it, which is the healthy direction.
21→15 CompilerServices.Binding uses CompilerServices.Diagnostics✕
- Connections
- 2 pairs of types, where a type in CompilerServices.Binding uses a type in CompilerServices.Diagnostics.
- The types involved
Feersum.CompilerServices.Binding.BinderCtx→Feersum.CompilerServices.Diagnostics.DiagnosticBagFeersum.CompilerServices.Binding.PatternCtx→Feersum.CompilerServices.Diagnostics.DiagnosticBag
- Direction
- CompilerServices.Binding uses CompilerServices.Diagnostics, so a change to CompilerServices.Diagnostics can break CompilerServices.Binding, while a change to CompilerServices.Binding can't break CompilerServices.Diagnostics.
- Position
- Below the diagonal: CompilerServices.Binding uses a module listed above it, which is the healthy direction.
22→12 CompilerServices.Binding.Stx uses CompilerServices.Text✕
- Connections
- 2 pairs of types, where a type in CompilerServices.Binding.Stx uses a type in CompilerServices.Text.
- The types involved
Feersum.CompilerServices.Binding.Stx.Stx→Feersum.CompilerServices.Text.DocIdFeersum.CompilerServices.Binding.Stx.Stx→Feersum.CompilerServices.Text.SourceRegistry
- Direction
- CompilerServices.Binding.Stx uses CompilerServices.Text, so a change to CompilerServices.Text can break CompilerServices.Binding.Stx, while a change to CompilerServices.Binding.Stx can't break CompilerServices.Text.
- Position
- Below the diagonal: CompilerServices.Binding.Stx uses a module listed above it, which is the healthy direction.
22→15 CompilerServices.Binding.Stx uses CompilerServices.Diagnostics✕
- Connections
- 1 pair of types, where a type in CompilerServices.Binding.Stx uses a type in CompilerServices.Diagnostics.
- The types involved
Feersum.CompilerServices.Binding.Stx.Stx→Feersum.CompilerServices.Diagnostics.DiagnosticBag
- Direction
- CompilerServices.Binding.Stx uses CompilerServices.Diagnostics, so a change to CompilerServices.Diagnostics can break CompilerServices.Binding.Stx, while a change to CompilerServices.Binding.Stx can't break CompilerServices.Diagnostics.
- Position
- Below the diagonal: CompilerServices.Binding.Stx uses a module listed above it, which is the healthy direction.
22→18 CompilerServices.Binding.Stx uses CompilerServices.Syntax.Tree✕
- Connections
- 1 pair of types, where a type in CompilerServices.Binding.Stx uses a type in CompilerServices.Syntax.Tree.
- The types involved
Feersum.CompilerServices.Binding.Stx.Stx→Feersum.CompilerServices.Syntax.Tree.Expression
- Direction
- CompilerServices.Binding.Stx uses CompilerServices.Syntax.Tree, so a change to CompilerServices.Syntax.Tree can break CompilerServices.Binding.Stx, while a change to CompilerServices.Binding.Stx can't break CompilerServices.Syntax.Tree.
- Position
- Below the diagonal: CompilerServices.Binding.Stx uses a module listed above it, which is the healthy direction.
23→12 CompilerServices.Compile uses CompilerServices.Text✕
- Connections
- 1 pair of types, where a type in CompilerServices.Compile uses a type in CompilerServices.Text.
- The types involved
Feersum.CompilerServices.Compile.CompileInput→Feersum.CompilerServices.Text.SourceRegistry
- Direction
- CompilerServices.Compile uses CompilerServices.Text, so a change to CompilerServices.Text can break CompilerServices.Compile, while a change to CompilerServices.Compile can't break CompilerServices.Text.
- Position
- Below the diagonal: CompilerServices.Compile uses a module listed above it, which is the healthy direction.
23→18 CompilerServices.Compile uses CompilerServices.Syntax.Tree✕
- Connections
- 1 pair of types, where a type in CompilerServices.Compile uses a type in CompilerServices.Syntax.Tree.
- The types involved
Feersum.CompilerServices.Compile.CompileInput→Feersum.CompilerServices.Syntax.Tree.ScriptProgram
- Direction
- CompilerServices.Compile uses CompilerServices.Syntax.Tree, so a change to CompilerServices.Syntax.Tree can break CompilerServices.Compile, while a change to CompilerServices.Compile can't break CompilerServices.Syntax.Tree.
- Position
- Below the diagonal: CompilerServices.Compile uses a module listed above it, which is the healthy direction.
24→18 CompilerServices.Syntax.Factories uses CompilerServices.Syntax.Tree✕
- Connections
- 3 pairs of types, where a type in CompilerServices.Syntax.Factories uses a type in CompilerServices.Syntax.Tree.
- The types involved
Feersum.CompilerServices.Syntax.Factories.Factories→Feersum.CompilerServices.Syntax.Tree.ExpressionFeersum.CompilerServices.Syntax.Factories.Factories→Feersum.CompilerServices.Syntax.Tree.ProgramFeersum.CompilerServices.Syntax.Factories.Factories→Feersum.CompilerServices.Syntax.Tree.ScriptProgram
- Direction
- CompilerServices.Syntax.Factories uses CompilerServices.Syntax.Tree, so a change to CompilerServices.Syntax.Tree can break CompilerServices.Syntax.Factories, while a change to CompilerServices.Syntax.Factories can't break CompilerServices.Syntax.Tree.
- Position
- Below the diagonal: CompilerServices.Syntax.Factories uses a module listed above it, which is the healthy direction.
25→18 CompilerServices.Syntax.Factories.Convenience uses CompilerServices.Syntax.Tree✕
- Connections
- 1 pair of types, where a type in CompilerServices.Syntax.Factories.Convenience uses a type in CompilerServices.Syntax.Tree.
- The types involved
Feersum.CompilerServices.Syntax.Factories.Convenience.Convenience→Feersum.CompilerServices.Syntax.Tree.Expression
- Direction
- CompilerServices.Syntax.Factories.Convenience uses CompilerServices.Syntax.Tree, so a change to CompilerServices.Syntax.Tree can break CompilerServices.Syntax.Factories.Convenience, while a change to CompilerServices.Syntax.Factories.Convenience can't break CompilerServices.Syntax.Tree.
- Position
- Below the diagonal: CompilerServices.Syntax.Factories.Convenience uses a module listed above it, which is the healthy direction.
26→18 CompilerServices.Syntax.Tree.Patterns uses CompilerServices.Syntax.Tree✕
- Connections
- 2 pairs of types, where a type in CompilerServices.Syntax.Tree.Patterns uses a type in CompilerServices.Syntax.Tree.
- The types involved
Feersum.CompilerServices.Syntax.Tree.Patterns.Patterns→Feersum.CompilerServices.Syntax.Tree.ConstantValueFeersum.CompilerServices.Syntax.Tree.Patterns.Patterns→Feersum.CompilerServices.Syntax.Tree.Expression
- Direction
- CompilerServices.Syntax.Tree.Patterns uses CompilerServices.Syntax.Tree, so a change to CompilerServices.Syntax.Tree can break CompilerServices.Syntax.Tree.Patterns, while a change to CompilerServices.Syntax.Tree.Patterns can't break CompilerServices.Syntax.Tree.
- Position
- Below the diagonal: CompilerServices.Syntax.Tree.Patterns uses a module listed above it, which is the healthy direction.
27→18 CompilerServices.Syntax.Tree.SyntaxUtils uses CompilerServices.Syntax.Tree✕
- Connections
- 1 pair of types, where a type in CompilerServices.Syntax.Tree.SyntaxUtils uses a type in CompilerServices.Syntax.Tree.
- The types involved
Feersum.CompilerServices.Syntax.Tree.SyntaxUtils.SyntaxUtils→Feersum.CompilerServices.Syntax.Tree.AstKind
- Direction
- CompilerServices.Syntax.Tree.SyntaxUtils uses CompilerServices.Syntax.Tree, so a change to CompilerServices.Syntax.Tree can break CompilerServices.Syntax.Tree.SyntaxUtils, while a change to CompilerServices.Syntax.Tree.SyntaxUtils can't break CompilerServices.Syntax.Tree.
- Position
- Below the diagonal: CompilerServices.Syntax.Tree.SyntaxUtils uses a module listed above it, which is the healthy direction.
28→13 CompilerServices.Syntax.Tree.Utils uses CompilerServices.Utils.Result✕
- Connections
- 1 pair of types, where a type in CompilerServices.Syntax.Tree.Utils uses a type in CompilerServices.Utils.Result.
- The types involved
Feersum.CompilerServices.Syntax.Tree.Utils.Utils→Feersum.CompilerServices.Utils.Result.Result
- Direction
- CompilerServices.Syntax.Tree.Utils uses CompilerServices.Utils.Result, so a change to CompilerServices.Utils.Result can break CompilerServices.Syntax.Tree.Utils, while a change to CompilerServices.Syntax.Tree.Utils can't break CompilerServices.Utils.Result.
- Position
- Below the diagonal: CompilerServices.Syntax.Tree.Utils uses a module listed above it, which is the healthy direction.
28→18 CompilerServices.Syntax.Tree.Utils uses CompilerServices.Syntax.Tree✕
- Connections
- 1 pair of types, where a type in CompilerServices.Syntax.Tree.Utils uses a type in CompilerServices.Syntax.Tree.
- The types involved
Feersum.CompilerServices.Syntax.Tree.Utils.Utils→Feersum.CompilerServices.Syntax.Tree.AstKind
- Direction
- CompilerServices.Syntax.Tree.Utils uses CompilerServices.Syntax.Tree, so a change to CompilerServices.Syntax.Tree can break CompilerServices.Syntax.Tree.Utils, while a change to CompilerServices.Syntax.Tree.Utils can't break CompilerServices.Syntax.Tree.
- Position
- Below the diagonal: CompilerServices.Syntax.Tree.Utils uses a module listed above it, which is the healthy direction.
29→12 CompilerServices.Binding.Binder uses CompilerServices.Text✕
- Connections
- 1 pair of types, where a type in CompilerServices.Binding.Binder uses a type in CompilerServices.Text.
- The types involved
Feersum.CompilerServices.Binding.Binder.Binder→Feersum.CompilerServices.Text.SourceRegistry
- Direction
- CompilerServices.Binding.Binder uses CompilerServices.Text, so a change to CompilerServices.Text can break CompilerServices.Binding.Binder, while a change to CompilerServices.Binding.Binder can't break CompilerServices.Text.
- Position
- Below the diagonal: CompilerServices.Binding.Binder uses a module listed above it, which is the healthy direction.
29→18 CompilerServices.Binding.Binder uses CompilerServices.Syntax.Tree✕
- Connections
- 1 pair of types, where a type in CompilerServices.Binding.Binder uses a type in CompilerServices.Syntax.Tree.
- The types involved
Feersum.CompilerServices.Binding.Binder.Binder→Feersum.CompilerServices.Syntax.Tree.ScriptProgram
- Direction
- CompilerServices.Binding.Binder uses CompilerServices.Syntax.Tree, so a change to CompilerServices.Syntax.Tree can break CompilerServices.Binding.Binder, while a change to CompilerServices.Binding.Binder can't break CompilerServices.Syntax.Tree.
- Position
- Below the diagonal: CompilerServices.Binding.Binder uses a module listed above it, which is the healthy direction.
29→21 CompilerServices.Binding.Binder uses CompilerServices.Binding✕
- Connections
- 2 pairs of types, where a type in CompilerServices.Binding.Binder uses a type in CompilerServices.Binding.
- The types involved
Feersum.CompilerServices.Binding.Binder.Binder→Feersum.CompilerServices.Binding.BinderCtxFeersum.CompilerServices.Binding.Binder.Binder→Feersum.CompilerServices.Binding.BoundSyntaxTree
- Direction
- CompilerServices.Binding.Binder uses CompilerServices.Binding, so a change to CompilerServices.Binding can break CompilerServices.Binding.Binder, while a change to CompilerServices.Binding.Binder can't break CompilerServices.Binding.
- Position
- Below the diagonal: CompilerServices.Binding.Binder uses a module listed above it, which is the healthy direction.
30→21 CompilerServices.Binding.FrameCtx uses CompilerServices.Binding✕
- Connections
- 3 pairs of types, where a type in CompilerServices.Binding.FrameCtx uses a type in CompilerServices.Binding.
- The types involved
Feersum.CompilerServices.Binding.FrameCtx.FrameCtx→Feersum.CompilerServices.Binding.BoundBodyFeersum.CompilerServices.Binding.FrameCtx.FrameCtx→Feersum.CompilerServices.Binding.BoundExprFeersum.CompilerServices.Binding.FrameCtx.FrameCtx→Feersum.CompilerServices.Binding.Ident
- Direction
- CompilerServices.Binding.FrameCtx uses CompilerServices.Binding, so a change to CompilerServices.Binding can break CompilerServices.Binding.FrameCtx, while a change to CompilerServices.Binding.FrameCtx can't break CompilerServices.Binding.
- Position
- Below the diagonal: CompilerServices.Binding.FrameCtx uses a module listed above it, which is the healthy direction.
31→12 CompilerServices.Binding.Impl uses CompilerServices.Text✕
- Connections
- 1 pair of types, where a type in CompilerServices.Binding.Impl uses a type in CompilerServices.Text.
- The types involved
Feersum.CompilerServices.Binding.Impl.Impl→Feersum.CompilerServices.Text.TextLocation
- Direction
- CompilerServices.Binding.Impl uses CompilerServices.Text, so a change to CompilerServices.Text can break CompilerServices.Binding.Impl, while a change to CompilerServices.Binding.Impl can't break CompilerServices.Text.
- Position
- Below the diagonal: CompilerServices.Binding.Impl uses a module listed above it, which is the healthy direction.
31→21 CompilerServices.Binding.Impl uses CompilerServices.Binding✕
- Connections
- 12 pairs of types, where a type in CompilerServices.Binding.Impl uses a type in CompilerServices.Binding.
- The types involved
Feersum.CompilerServices.Binding.Impl.Impl→Feersum.CompilerServices.Binding.BinderCtxFeersum.CompilerServices.Binding.Impl.Impl→Feersum.CompilerServices.Binding.BoundBodyFeersum.CompilerServices.Binding.Impl.Impl→Feersum.CompilerServices.Binding.BoundExprFeersum.CompilerServices.Binding.Impl.Impl→Feersum.CompilerServices.Binding.BoundFormalsFeersum.CompilerServices.Binding.Impl.Impl→Feersum.CompilerServices.Binding.FrameCtxFeersum.CompilerServices.Binding.Impl.Impl→Feersum.CompilerServices.Binding.IdentFeersum.CompilerServices.Binding.Impl.Impl→Feersum.CompilerServices.Binding.LibraryDefinitionFeersum.CompilerServices.Binding.Impl.Impl→Feersum.CompilerServices.Binding.LibrarySignatureFeersum.CompilerServices.Binding.Impl.Impl→Feersum.CompilerServices.Binding.NameResolutionFeersum.CompilerServices.Binding.Impl.Impl→Feersum.CompilerServices.Binding.SpecialFormKindFeersum.CompilerServices.Binding.Impl.Impl→Feersum.CompilerServices.Binding.StorageRefFeersum.CompilerServices.Binding.Impl.Impl→Feersum.CompilerServices.Binding.Stx
- Direction
- CompilerServices.Binding.Impl uses CompilerServices.Binding, so a change to CompilerServices.Binding can break CompilerServices.Binding.Impl, while a change to CompilerServices.Binding.Impl can't break CompilerServices.Binding.
- Position
- Below the diagonal: CompilerServices.Binding.Impl uses a module listed above it, which is the healthy direction.
32→21 CompilerServices.Binding.Libraries uses CompilerServices.Binding✕
- Connections
- 1 pair of types, where a type in CompilerServices.Binding.Libraries uses a type in CompilerServices.Binding.
- The types involved
Feersum.CompilerServices.Binding.Libraries.Libraries→Feersum.CompilerServices.Binding.Stx
- Direction
- CompilerServices.Binding.Libraries uses CompilerServices.Binding, so a change to CompilerServices.Binding can break CompilerServices.Binding.Libraries, while a change to CompilerServices.Binding.Libraries can't break CompilerServices.Binding.
- Position
- Below the diagonal: CompilerServices.Binding.Libraries uses a module listed above it, which is the healthy direction.
33→21 CompilerServices.Binding.Lower uses CompilerServices.Binding✕
- Connections
- 1 pair of types, where a type in CompilerServices.Binding.Lower uses a type in CompilerServices.Binding.
- The types involved
Feersum.CompilerServices.Binding.Lower.Lower→Feersum.CompilerServices.Binding.BoundSyntaxTree
- Direction
- CompilerServices.Binding.Lower uses CompilerServices.Binding, so a change to CompilerServices.Binding can break CompilerServices.Binding.Lower, while a change to CompilerServices.Binding.Lower can't break CompilerServices.Binding.
- Position
- Below the diagonal: CompilerServices.Binding.Lower uses a module listed above it, which is the healthy direction.
34→15 CompilerServices.Binding.MacroParse uses CompilerServices.Diagnostics✕
- Connections
- 1 pair of types, where a type in CompilerServices.Binding.MacroParse uses a type in CompilerServices.Diagnostics.
- The types involved
Feersum.CompilerServices.Binding.MacroParse.MacroParse→Feersum.CompilerServices.Diagnostics.DiagnosticBag
- Direction
- CompilerServices.Binding.MacroParse uses CompilerServices.Diagnostics, so a change to CompilerServices.Diagnostics can break CompilerServices.Binding.MacroParse, while a change to CompilerServices.Binding.MacroParse can't break CompilerServices.Diagnostics.
- Position
- Below the diagonal: CompilerServices.Binding.MacroParse uses a module listed above it, which is the healthy direction.
34→21 CompilerServices.Binding.MacroParse uses CompilerServices.Binding✕
- Connections
- 3 pairs of types, where a type in CompilerServices.Binding.MacroParse uses a type in CompilerServices.Binding.
- The types involved
Feersum.CompilerServices.Binding.MacroParse.MacroParse→Feersum.CompilerServices.Binding.MacroTemplateFeersum.CompilerServices.Binding.MacroParse.MacroParse→Feersum.CompilerServices.Binding.PatternCtxFeersum.CompilerServices.Binding.MacroParse.MacroParse→Feersum.CompilerServices.Binding.Stx
- Direction
- CompilerServices.Binding.MacroParse uses CompilerServices.Binding, so a change to CompilerServices.Binding can break CompilerServices.Binding.MacroParse, while a change to CompilerServices.Binding.MacroParse can't break CompilerServices.Binding.
- Position
- Below the diagonal: CompilerServices.Binding.MacroParse uses a module listed above it, which is the healthy direction.
35→13 CompilerServices.Binding.Macros uses CompilerServices.Utils.Result✕
- Connections
- 1 pair of types, where a type in CompilerServices.Binding.Macros uses a type in CompilerServices.Utils.Result.
- The types involved
Feersum.CompilerServices.Binding.Macros.Macros→Feersum.CompilerServices.Utils.Result.Result
- Direction
- CompilerServices.Binding.Macros uses CompilerServices.Utils.Result, so a change to CompilerServices.Utils.Result can break CompilerServices.Binding.Macros, while a change to CompilerServices.Binding.Macros can't break CompilerServices.Utils.Result.
- Position
- Below the diagonal: CompilerServices.Binding.Macros uses a module listed above it, which is the healthy direction.
35→15 CompilerServices.Binding.Macros uses CompilerServices.Diagnostics✕
- Connections
- 1 pair of types, where a type in CompilerServices.Binding.Macros uses a type in CompilerServices.Diagnostics.
- The types involved
Feersum.CompilerServices.Binding.Macros.Macros→Feersum.CompilerServices.Diagnostics.DiagnosticBag
- Direction
- CompilerServices.Binding.Macros uses CompilerServices.Diagnostics, so a change to CompilerServices.Diagnostics can break CompilerServices.Binding.Macros, while a change to CompilerServices.Binding.Macros can't break CompilerServices.Diagnostics.
- Position
- Below the diagonal: CompilerServices.Binding.Macros uses a module listed above it, which is the healthy direction.
35→21 CompilerServices.Binding.Macros uses CompilerServices.Binding✕
- Connections
- 6 pairs of types, where a type in CompilerServices.Binding.Macros uses a type in CompilerServices.Binding.
- The types involved
Feersum.CompilerServices.Binding.Macros.Macros→Feersum.CompilerServices.Binding.MacroFeersum.CompilerServices.Binding.Macros.Macros→Feersum.CompilerServices.Binding.MacroBindingsFeersum.CompilerServices.Binding.Macros.Macros→Feersum.CompilerServices.Binding.MacroPatternFeersum.CompilerServices.Binding.Macros.Macros→Feersum.CompilerServices.Binding.MacroTemplateFeersum.CompilerServices.Binding.Macros.Macros→Feersum.CompilerServices.Binding.MacroTemplateElementFeersum.CompilerServices.Binding.Macros.Macros→Feersum.CompilerServices.Binding.Stx
- Direction
- CompilerServices.Binding.Macros uses CompilerServices.Binding, so a change to CompilerServices.Binding can break CompilerServices.Binding.Macros, while a change to CompilerServices.Binding.Macros can't break CompilerServices.Binding.
- Position
- Below the diagonal: CompilerServices.Binding.Macros uses a module listed above it, which is the healthy direction.
36→21 CompilerServices.Binding.ResolutionEnv uses CompilerServices.Binding✕
- Connections
- 2 pairs of types, where a type in CompilerServices.Binding.ResolutionEnv uses a type in CompilerServices.Binding.
- The types involved
Feersum.CompilerServices.Binding.ResolutionEnv.ResolutionEnv→Feersum.CompilerServices.Binding.IdentFeersum.CompilerServices.Binding.ResolutionEnv.ResolutionEnv→Feersum.CompilerServices.Binding.StorageRef
- Direction
- CompilerServices.Binding.ResolutionEnv uses CompilerServices.Binding, so a change to CompilerServices.Binding can break CompilerServices.Binding.ResolutionEnv, while a change to CompilerServices.Binding.ResolutionEnv can't break CompilerServices.Binding.
- Position
- Below the diagonal: CompilerServices.Binding.ResolutionEnv uses a module listed above it, which is the healthy direction.
37→13 CompilerServices.Binding.Utils uses CompilerServices.Utils.Result✕
- Connections
- 1 pair of types, where a type in CompilerServices.Binding.Utils uses a type in CompilerServices.Utils.Result.
- The types involved
Feersum.CompilerServices.Binding.Utils.Utils→Feersum.CompilerServices.Utils.Result.Result
- Direction
- CompilerServices.Binding.Utils uses CompilerServices.Utils.Result, so a change to CompilerServices.Utils.Result can break CompilerServices.Binding.Utils, while a change to CompilerServices.Binding.Utils can't break CompilerServices.Utils.Result.
- Position
- Below the diagonal: CompilerServices.Binding.Utils uses a module listed above it, which is the healthy direction.
37→15 CompilerServices.Binding.Utils uses CompilerServices.Diagnostics✕
- Connections
- 1 pair of types, where a type in CompilerServices.Binding.Utils uses a type in CompilerServices.Diagnostics.
- The types involved
Feersum.CompilerServices.Binding.Utils.Utils→Feersum.CompilerServices.Diagnostics.DiagnosticBag
- Direction
- CompilerServices.Binding.Utils uses CompilerServices.Diagnostics, so a change to CompilerServices.Diagnostics can break CompilerServices.Binding.Utils, while a change to CompilerServices.Binding.Utils can't break CompilerServices.Diagnostics.
- Position
- Below the diagonal: CompilerServices.Binding.Utils uses a module listed above it, which is the healthy direction.
37→21 CompilerServices.Binding.Utils uses CompilerServices.Binding✕
- Connections
- 4 pairs of types, where a type in CompilerServices.Binding.Utils uses a type in CompilerServices.Binding.
- The types involved
Feersum.CompilerServices.Binding.Utils.Utils→Feersum.CompilerServices.Binding.ImportSetFeersum.CompilerServices.Binding.Utils.Utils→Feersum.CompilerServices.Binding.LibraryDeclarationFeersum.CompilerServices.Binding.Utils.Utils→Feersum.CompilerServices.Binding.LibrarySignatureFeersum.CompilerServices.Binding.Utils.Utils→Feersum.CompilerServices.Binding.Stx
- Direction
- CompilerServices.Binding.Utils uses CompilerServices.Binding, so a change to CompilerServices.Binding can break CompilerServices.Binding.Utils, while a change to CompilerServices.Binding.Utils can't break CompilerServices.Binding.
- Position
- Below the diagonal: CompilerServices.Binding.Utils uses a module listed above it, which is the healthy direction.
38→1 CompilerServices.Compile.Compilation uses CompilerServices✕
- Connections
- 1 pair of types, where a type in CompilerServices.Compile.Compilation uses a type in CompilerServices.
- The types involved
Feersum.CompilerServices.Compile.Compilation.Compilation→Feersum.CompilerServices.CompilationOptions
- Direction
- CompilerServices.Compile.Compilation uses CompilerServices, so a change to CompilerServices can break CompilerServices.Compile.Compilation, while a change to CompilerServices.Compile.Compilation can't break CompilerServices.
- Position
- Below the diagonal: CompilerServices.Compile.Compilation uses a module listed above it, which is the healthy direction.
38→23 CompilerServices.Compile.Compilation uses CompilerServices.Compile✕
- Connections
- 1 pair of types, where a type in CompilerServices.Compile.Compilation uses a type in CompilerServices.Compile.
- The types involved
Feersum.CompilerServices.Compile.Compilation.Compilation→Feersum.CompilerServices.Compile.CompileInput
- Direction
- CompilerServices.Compile.Compilation uses CompilerServices.Compile, so a change to CompilerServices.Compile can break CompilerServices.Compile.Compilation, while a change to CompilerServices.Compile.Compilation can't break CompilerServices.Compile.
- Position
- Below the diagonal: CompilerServices.Compile.Compilation uses a module listed above it, which is the healthy direction.
39→21 CompilerServices.Compile.Emit uses CompilerServices.Binding✕
- Connections
- 1 pair of types, where a type in CompilerServices.Compile.Emit uses a type in CompilerServices.Binding.
- The types involved
Feersum.CompilerServices.Compile.Emit.Emit→Feersum.CompilerServices.Binding.BoundSyntaxTree
- Direction
- CompilerServices.Compile.Emit uses CompilerServices.Binding, so a change to CompilerServices.Binding can break CompilerServices.Compile.Emit, while a change to CompilerServices.Compile.Emit can't break CompilerServices.Binding.
- Position
- Below the diagonal: CompilerServices.Compile.Emit uses a module listed above it, which is the healthy direction.
40→21 CompilerServices.Compile.Utils uses CompilerServices.Binding✕
- Connections
- 3 pairs of types, where a type in CompilerServices.Compile.Utils uses a type in CompilerServices.Binding.
- The types involved
Feersum.CompilerServices.Compile.Utils.Utils→Feersum.CompilerServices.Binding.BoundBodyFeersum.CompilerServices.Compile.Utils.Utils→Feersum.CompilerServices.Binding.BoundDatumFeersum.CompilerServices.Compile.Utils.Utils→Feersum.CompilerServices.Binding.BoundExpr
- Direction
- CompilerServices.Compile.Utils uses CompilerServices.Binding, so a change to CompilerServices.Binding can break CompilerServices.Compile.Utils, while a change to CompilerServices.Compile.Utils can't break CompilerServices.Binding.
- Position
- Below the diagonal: CompilerServices.Compile.Utils uses a module listed above it, which is the healthy direction.
40→23 CompilerServices.Compile.Utils uses CompilerServices.Compile✕
- Connections
- 2 pairs of types, where a type in CompilerServices.Compile.Utils uses a type in CompilerServices.Compile.
- The types involved
Feersum.CompilerServices.Compile.Utils.Utils→Feersum.CompilerServices.Compile.CoreTypesFeersum.CompilerServices.Compile.Utils.Utils→Feersum.CompilerServices.Compile.EmitCtx
- Direction
- CompilerServices.Compile.Utils uses CompilerServices.Compile, so a change to CompilerServices.Compile can break CompilerServices.Compile.Utils, while a change to CompilerServices.Compile.Utils can't break CompilerServices.Compile.
- Position
- Below the diagonal: CompilerServices.Compile.Utils 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 | 19 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 5 | Medium |
Roadmap
Top priorities: Reconcile the README with reality: docs/10-language-reference/README.md links to `./special-forms/`, but `docs/10-language-reference/special-forms` does not exist; docs/10-language-reference/README.md links to `./standard-procedures/`, but `docs/10-language-reference/standard-procedures` does not exist; docs/design-docs/README.md links to `./syntax-trees/`, but `docs/design-docs/syntax-trees` does not exist; docs/design-docs/README.md links to `./syntactic-closures-expander/`, but `docs/design-docs/syntactic-closures-expander` does not exist; Grow the ADR log (currently 3) — reach 8 to raise the maturity tier; document significant decisions as they're made; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Reconcile the README with reality: docs/10-language-reference/README.md links to `./special-forms/`, but `docs/10-language-reference/special-forms` does not exist; docs/10-language-reference/README.md links to `./standard-procedures/`, but `docs/10-language-reference/standard-procedures` does not exist; docs/design-docs/README.md links to `./syntax-trees/`, but `docs/design-docs/syntax-trees` does not exist; docs/design-docs/README.md links to `./syntactic-closures-expander/`, but `docs/design-docs/syntactic-closures-expander` does not exist. | +4.3 pts | Medium | Documentation accuracy |
| Grow the ADR log (currently 3) — reach 8 to raise the maturity tier; document significant decisions as they're made. | +3.4 pts | Medium | Architecture documentation |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +2.1 pts | Medium | Documentation (README) |
| Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where Watchdog can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it. | +2.1 pts | Medium | Deployment & Rollback |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.1 pts | Medium | Release Hygiene |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). | +0.9 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.7 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.7 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/Serehfa/Time.cs | 6.9 | Near-clean | Explicit Debt: FixmeComment |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| src/Directory.Build.props | 7.6 | Near-clean | Explicit Debt: NoWarnInCsproj |
| src/Serehfa/ByteVectors.cs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/Serehfa/RandomBits.cs | 8.2 | Near-clean | Explicit Debt: FixmeComment |
| src/Feersum.CompilerServices/Compile/Emit.fs | 8.5 | Near-clean | God Classes: FileTooLong: Compile/Emit.fs |
| src/Feersum.CompilerServices/Binding/Binder.fs | 8.5 | Near-clean | God Classes: FileTooLong: Binding/Binder.fs |
| src/Serehfa/Equivalence.cs | 8.5 | Near-clean | Code Duplication: Duplicated block (8 lines × 2) |
| docs/design-docs/01-syntax-trees.md | 9.5 | Near-clean | Architectural Integrity: Classify ADR enforcement: Syntax Trees |
| docs/design-docs/02-document-service.md | 9.5 | Near-clean | Architectural Integrity: Classify ADR enforcement: Document Service |
| docs/design-docs/04-syntactic-closures-expander.md | 9.5 | Near-clean | Architectural Integrity: Classify ADR enforcement: Syntactic Closures Expansion and Binding |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 57 of 57 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 57 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, 35 of 43 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D1 Cyclomatic Complexity — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Most of this repository's production source (.fs) had no cyclomatic complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D2 Cognitive Complexity — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Most of this repository's production source (.fs) had no cognitive complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The test suite couldn't be built/run in-image and no coverage report is committed, so line coverage was not measured — and it is EXCLUDED from the score rather than scored on a LoC-ratio proxy. Your test projects already reference a coverage collector, but no CI step we found runs the tests with it, so there is no report to hand us — run them with `--collect:"XPlat Code Coverage"` and commit (or publish into the working tree) the coverage.cobertura.xml it writes. You can widen what we reach: optional: your test projects already reference a coverage collector, but no CI step we found runs the tests with it, so there is no report to hand us — run them with `--collect:"XPlat Code Coverage"` and commit (or publish into the working tree) the coverage.cobertura.xml it writes, or make the suite runnable in-image, and real coverage will be measured.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
- D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: src/Feersum/Feersum.fsproj : error NU1507: Warning As Error: There are 2 package sources defined in your configuration. When using central package management, map your package sources with package source mapping (https://aka.ms/nuget-package-sourc….
- D15 Churn × Complexity Hotspots — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. A hotspot is churn × complexity. Churn was measured (13867 line(s) across the 90-day window), but no complexity could be computed for .fs, which is most of this repository's production code — so every churned file would score as complexity 0 and the hotspot list would be empty no matter how tangled the code is. Not scored — this is a gap in the analysis run, not a finding about this repository.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 707 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 1 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D17 Explicit Debt — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'examples/HelloWorld/HelloWorld.scmproj' because the file extension '.scmproj' is not associated with a language.
- D17 Explicit Debt — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 6 deducted marker(s) and the 0.4/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (5,973 lines, 81% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D39 IL Efficiency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. IL NOT MEASURED: the analyzer's build of this repository exited 1 and the cause could not be attributed, so no assemblies were produced and there was no IL to read. We do not read it as a defect in the repository: an unattributed failure leans OURS. D18 owns the question of whether this repository builds; it was not answered here.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- 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.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- 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.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- 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.
- 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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- 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
D3 · God Classes
2 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 FileTooLong finding(s) in God Classes — start with Emit.fs, Binder.fs. — One of this dimension's main actionable groups (2 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
1 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with Equivalence.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
1 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 1 classes have LCOM4 above 3.
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Cycles found: 0.
What to do
- Resolve the 3 Classify ADR enforcement finding(s) in Architectural Integrity — start with 01-syntax-trees.md, 02-document-service.md, 04-syntactic-closures-expander.md. — One of this dimension's main actionable groups (3 recommendation-level).
- Enforce Architectural Integrity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 147 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 12 direct `PackageReference`(s), and 135 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.
D17 · Explicit Debt
6 deducted debt markers + unmeasured dead symbols across 1392 LoC in the .NET projects (0.4/KLoC) → score 9.1. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (81% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
What to do
- Resolve the 1 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 4 FixmeComment finding(s) in Explicit Debt — start with Time.cs (3), RandomBits.cs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with ByteVectors.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 11 document(s) read across 2 unit(s).
D20 · ADR Quality
0 of 3 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
D26 · Project Cohesion
0 of 1 projects flagged as possibly oversized/incoherent.
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)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
19 finding(s): 0 critical, 19 high, 0 medium, 0 low. 15 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- 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 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 15 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (15 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 29 of the 59 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 7 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX8 · Test isolation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 1 of 1 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
What to do
- Grow the ADR log (currently 3) — reach 8 to raise the maturity tier; document significant decisions as they're made.
M3 · Folder & project structure
M4 · Documentation accuracy
- docs/10-language-reference/README.md links to `./special-forms/`, but `docs/10-language-reference/special-forms` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/10-language-reference/README.md:13
- docs/10-language-reference/README.md links to `./standard-procedures/`, but `docs/10-language-reference/standard-procedures` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/10-language-reference/README.md:14
- docs/design-docs/README.md links to `./syntax-trees/`, but `docs/design-docs/syntax-trees` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/README.md:7
- docs/design-docs/README.md links to `./syntactic-closures-expander/`, but `docs/design-docs/syntactic-closures-expander` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/README.md:8
What to do
- Reconcile the README with reality: docs/10-language-reference/README.md links to `./special-forms/`, but `docs/10-language-reference/special-forms` does not exist; docs/10-language-reference/README.md links to `./standard-procedures/`, but `docs/10-language-reference/standard-procedures` does not exist; docs/design-docs/README.md links to `./syntax-trees/`, but `docs/design-docs/syntax-trees` does not exist; docs/design-docs/README.md links to `./syntactic-closures-expander/`, but `docs/design-docs/syntactic-closures-expander` does not exist.
P1 · CI/CD gates
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 4778 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.
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.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where Watchdog can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 96% | Exemplary | Solid. |
| Architecture | 98% | Exemplary | Solid. |
| Maturity | 53% | Adequate — gated by M4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 56% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 62% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 61 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.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — no DI registrations detected
- AX2 Stateful singletons — no singleton implementations detected
- AX6 Interface segregation — no public interfaces
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — 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 — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — This is a dotnet-new template — authorization is deferred to the application you build from it. Add [Authorize]/policies (or imperative guards) when you wire up real users; until then there are no real endpoints to protect.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D1 Cyclomatic Complexity — cyclomatic complexity not measured — .fs exposed no member bodies
- D10 Test Quality — ~2493 lines of test source are present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not measured — no test run produced results
- D12 Dependency Hygiene — Dependency hygiene not measured
- D15 Churn × Complexity Hotspots — complexity unreadable for .fs — churn × complexity hotspots could not be measured
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .fs, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D2 Cognitive Complexity — cognitive complexity not measured — .fs exposed no member bodies
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; F# not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (7,365 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only; comments in this repository's .fs source were not judged.
- D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
- 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.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
- D8 Code Coverage — Coverage not measured
- D9 Test Distribution — Test source is present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 31 value object(s); 2 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
- P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no async method does work a token could cancel
- X5 Nullable reference types — no NRT-eligible projects
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 20 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- NoWarnInCsproj src/Directory.Build.props:5
- REDACTED
- REDACTED
Serious — 11 finding(s)
- FixmeComment src/Serehfa/RandomBits.cs:15
- FixmeComment src/Serehfa/Time.cs:17
- FixmeComment src/Serehfa/Time.cs:25
- FixmeComment src/Serehfa/Time.cs:33
- FileTooLong: Compile/Emit.fs src/Feersum.CompilerServices/Compile/Emit.fs
- FileTooLong: Binding/Binder.fs src/Feersum.CompilerServices/Binding/Binder.fs
- TodoComment src/Serehfa/ByteVectors.cs:24
- REDACTED
- REDACTED
- Duplicated block (8 lines × 2) src/Serehfa/Equivalence.cs:27
- Test suite runs only after the merge
Minor — 12 finding(s)
- README/code drift docs/10-language-reference/README.md:13
- README/code drift docs/10-language-reference/README.md:14
- README/code drift docs/design-docs/README.md:7
- README/code drift docs/design-docs/README.md:8
- Classify ADR enforcement: Syntax Trees docs/design-docs/01-syntax-trees.md
- Classify ADR enforcement: Document Service docs/design-docs/02-document-service.md
- Classify ADR enforcement: Syntactic Closures Expansion and Binding docs/design-docs/04-syntactic-closures-expander.md
- REDACTED
- REDACTED
- REDACTED
- No SAST
- No changelog
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e9928788b0844f84bc41a4b9c919eddc/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e9928788b0844f84bc41a4b9c919eddc/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude test/Feersum.Tests/_snapshots . | 19 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (no readable dependency manifest) | — | none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet). | 0 | — |