Executive summary
MagnusOpera/FScript falls short of our standard for a preview release because we found no logging, tracing or health checks in the code and no automated security scanning of the code, its secrets or its dependencies. It scores 54 out of 100 and is rated Adequate, and 57 of its 60 critical findings are security problems.
Production Readiness, at 48, is the weakest lens and counts most in the score. The best first step is handling the discarded errors, worth about 4 points. Adding a diagnostic log would lift Production Readiness itself, also worth about 4. Raising Production Readiness to 62 would lift the score to about 57.
Forty-seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Seven secrets can leak from the build pipeline, and three errors are caught and ignored, so failures can go unnoticed. Pinning each tool to an exact version, limiting each secret to its own step and handling or logging the ignored errors would close these risks. Updating the vulnerable packages would fix the package with a known security hole, and passing outside input through environment variables would deal with the pipeline step that puts outside input straight into a shell command.
The product code is 31,107 lines, about €51,000 to rebuild.
If Production Readiness rose from 48 to 62, the lowest score rated Strong, the score would rise from 54 to about 57.
New since the last survey: 34 findings
- Code Duplication · Edited copy of a member (39 corresponding lines) src/FScript.LanguageServer/LspHandlers.cs
- Code Duplication · Duplicated block (22 lines × 2) src/FScript.LanguageServer/LspHandlers.cs
- Code Duplication · Duplicated block (5 lines × 2) src/FScript.Compiler/Lir.fs
- Code Duplication · Duplicated block (7 lines × 3) src/FScript.Language/Parser.fs
- Code Duplication · Duplicated block (7 lines × 2) src/FScript.Runtime/FsExterns.fs
- Code Duplication · Duplicated block (6 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs
- Code Duplication · Duplicated block (5 lines × 2) src/FScript.Runtime/RegexExterns.fs
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- IaC & Container Security · REDACTED
- IaC & Container Security · REDACTED
- Change Coupling · Change coupling: Ast.fs ↔ Lexer.fs src/FScript.Language/Ast.fs
- Supply-chain Provenance & Signing · REDACTED
- Code Duplication · Duplicated block (14 lines × 2 locations) vscode-fscript/extension.js
Fixed since the last survey: 306 findings
- Cyclomatic Complexity · CSharpBackend.emit (cyclomatic 706) src/FScript.Backend.CSharp/CSharpBackend.fs
- Cyclomatic Complexity · Parser.parseProgramWithSourceNameAndOrigin (cyclomatic 435) src/FScript.Language/Parser.fs
- Cyclomatic Complexity · TypeInfer.inferResolvedProgramWithRegistration (cyclomatic 237) src/FScript.Language/TypeInfer.fs
- Cyclomatic Complexity · LirValidation.validate (cyclomatic 198) src/FScript.Compiler/Lir.fs
- Cyclomatic Complexity · LirMonomorphization.specialize (cyclomatic 155) src/FScript.Compiler/LirMonomorphization.fs
- Cyclomatic Complexity · HirValidation.validate (cyclomatic 155) src/FScript.Compiler/HirValidation.fs
- Cyclomatic Complexity · TaskSharingAnalysis.analyze (cyclomatic 148) src/FScript.Language/TaskSharingAnalysis.fs
- Cyclomatic Complexity · LirInterpreter.evaluate (cyclomatic 128) src/FScript.Interpreter.Lir/LirInterpreter.fs
- Cyclomatic Complexity · LirCommonSubexpressions.optimize (cyclomatic 120) src/FScript.Compiler/LirCommonSubexpressions.fs
- Cyclomatic Complexity · LirInterpreter.invokeIntrinsic (cyclomatic 119) src/FScript.Interpreter.Lir/LirInterpreter.fs
- Cyclomatic Complexity · TypeInfer.inferExprRaw (cyclomatic 117) src/FScript.Language/TypeInfer.fs
- Cyclomatic Complexity · LirEffects.create (cyclomatic 116) src/FScript.Compiler/LirEffects.fs
- Cyclomatic Complexity · Lexer.tokenizeCore (cyclomatic 103) src/FScript.Language/Lexer.fs
- Cyclomatic Complexity · Eval.evalCompound (cyclomatic 90) src/FScript.Language/Eval.fs
- Cyclomatic Complexity · LspHandlers.handleDefinition (cyclomatic 82) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs
- Cyclomatic Complexity · SupportLibrary.invokeScalar (cyclomatic 80) src/FScript.Language/SupportLibrary.fs
- Cyclomatic Complexity · SupportCollections.invoke (cyclomatic 68) src/FScript.Language/SupportCollections.fs
- Cyclomatic Complexity · LspHandlers.handleReferences (cyclomatic 63) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs
- Cyclomatic Complexity · DotNetDeadCaptures.optimize (cyclomatic 62) src/FScript.Backend.DotNet/DotNetDeadCaptures.fs
- Cyclomatic Complexity · DotNetOptimization.optimizeCore (cyclomatic 61) src/FScript.Backend.DotNet/DotNetOptimization.fs
- Cyclomatic Complexity · Eval.patternMatch (cyclomatic 61) src/FScript.Language/Eval.fs
- Cyclomatic Complexity · Eval.valueMatchesTypeRef (cyclomatic 56) src/FScript.Language/Eval.fs
- Cyclomatic Complexity · DotNetSourceOptimization.optimize (cyclomatic 55) src/FScript.Backend.DotNet/DotNetSourceOptimization.fs
- Cyclomatic Complexity · DotNetCollectionRepresentations.optimize (cyclomatic 55) src/FScript.Backend.DotNet/DotNetCollectionRepresentations.fs
- Cyclomatic Complexity · LspHandlers.handleSignatureHelp (cyclomatic 55) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs
- Cyclomatic Complexity · Program.runCompileCommand (cyclomatic 54) src/FScript/Program.fs
- Cyclomatic Complexity · IncludeResolver.rewriteModuleScopedStatements (cyclomatic 53) src/FScript.Language/IncludeResolver.fs
- Cyclomatic Complexity · LirInterpreter.matchPlan (cyclomatic 53) src/FScript.Interpreter.Lir/LirInterpreter.fs
- Cyclomatic Complexity · DotNetIlInlining.cleanup (cyclomatic 52) src/FScript.Backend.DotNet/DotNetIlInlining.fs
- Cyclomatic Complexity · IrArtifact.writeExpression (cyclomatic 49) src/FScript.Compiler/IrArtifact.fs
- Cyclomatic Complexity · LirAggregateElimination.optimize (cyclomatic 48) src/FScript.Compiler/LirAggregateElimination.fs
- Cyclomatic Complexity · DotNetIlInlining.validate (cyclomatic 47) src/FScript.Backend.DotNet/DotNetIlInlining.fs
- Cyclomatic Complexity · Hir.format (cyclomatic 47) src/FScript.Compiler/Hir.fs
- Cyclomatic Complexity · DotNetIlInlining.pruneReferences (cyclomatic 46) src/FScript.Backend.DotNet/DotNetIlInlining.fs
- Cyclomatic Complexity · LspSymbols.buildResolvedLocalDefinitions (cyclomatic 46) src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs
- Cyclomatic Complexity · LirInterpreter.applyValue (cyclomatic 45) src/FScript.Interpreter.Lir/LirInterpreter.fs
- Cyclomatic Complexity · LspSymbols.buildSymbolsFromProgram (cyclomatic 45) src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs
- Cyclomatic Complexity · Lir.format (cyclomatic 44) src/FScript.Compiler/Lir.fs
- Cyclomatic Complexity · LirOptimization.simplify (cyclomatic 44) src/FScript.Compiler/Lir.fs
- Cyclomatic Complexity · JavaScript.valueFromJs (cyclomatic 44) src/FScript.JavaScript/Library.fs
- Cyclomatic Complexity · DebuggerEntry.RunHost (cyclomatic 43) src/FScript.DebugAdapter/DebuggerEntry.cs
- Cyclomatic Complexity · TypeInfer.inferProgramWithExternsRawAndLocals (cyclomatic 42) src/FScript.Language/TypeInfer.fs
- Cyclomatic Complexity · HostInterop.prepareCall (cyclomatic 42) src/FScript.Language/HostInterop.fs
- Cyclomatic Complexity · LirInterpreter.invokeSupport (cyclomatic 42) src/FScript.Interpreter.Lir/LirInterpreter.fs
- Cyclomatic Complexity · LspSymbols.collectPatternVariableSpans (cyclomatic 42) src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs
- Cyclomatic Complexity · EnvironmentLoader.loadCore (cyclomatic 42) src/FScript.Runtime/EnvironmentLoader.fs
- Cyclomatic Complexity · IrArtifact.readExpression (cyclomatic 41) src/FScript.Compiler/IrArtifact.fs
- Cyclomatic Complexity · TypeInfer.unify (cyclomatic 41) src/FScript.Language/TypeInfer.fs
- Cyclomatic Complexity · LspSymbols.buildLocalBindings (cyclomatic 41) src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs
- Cyclomatic Complexity · Eval.evaluateRegistered (cyclomatic 40) src/FScript.Language/Eval.fs
- Cyclomatic Complexity · LspSymbols.buildCallArgumentHints (cyclomatic 40) src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs
- Cyclomatic Complexity · LspServer.HandleRequest (cyclomatic 39) src/FScript.LanguageServer/LspServer.cs
- Cyclomatic Complexity · ClrBindings.pruneUnusedTypes (cyclomatic 39) src/FScript.Compiler/ClrBindings.fs
- Cyclomatic Complexity · ExtensionBridge.toLanguageRegistration (cyclomatic 39) src/FScript.Runtime/ExtensionBridge.fs
- Cyclomatic Complexity · DotNetIlInlining.rewrite (cyclomatic 38) src/FScript.Backend.DotNet/DotNetIlInlining.fs
- Cyclomatic Complexity · EnvironmentConfigurationModule.parse (cyclomatic 38) src/FScript.Runtime/EnvironmentConfiguration.fs
- Cyclomatic Complexity · LspSymbols.inferLocalTypesFromReturnedRecordFields (cyclomatic 36) src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs
- Cyclomatic Complexity · HirLowering.lowerResolvedExpression (cyclomatic 34) src/FScript.Compiler/HirLowering.fs
- Cyclomatic Complexity · LspSymbols.inferBestEffort (cyclomatic 34) src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs
- Cyclomatic Complexity · extension.activate (cyclomatic 34) vscode-fscript/extension.js
- Cyclomatic Complexity · DotNetCollectionFusion.optimize (cyclomatic 33) src/FScript.Backend.DotNet/DotNetCollectionFusion.fs
- Cyclomatic Complexity · LirOptimization.effect (cyclomatic 33) src/FScript.Compiler/Lir.fs
- Cyclomatic Complexity · LspSymbols.tryResolveTypeTargetAtPosition (cyclomatic 33) src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs
- Cyclomatic Complexity · LirOptimization.markTailCalls (cyclomatic 32) src/FScript.Compiler/Lir.fs
- Cyclomatic Complexity · Eval.binaryOperator (cyclomatic 32) src/FScript.Language/Eval.fs
- Cyclomatic Complexity · IrArtifact.writeType (cyclomatic 29) src/FScript.Compiler/IrArtifact.fs
- Cyclomatic Complexity · TypeInfer.inferPattern (cyclomatic 29) src/FScript.Language/TypeInfer.fs
- Cyclomatic Complexity · LspSymbols.makeCompletionItems (cyclomatic 28) src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs
- Cyclomatic Complexity · HostDecode.decodeJson (cyclomatic 28) src/FScript.Runtime/Decode.fs
- Cyclomatic Complexity · extension.registerDebugger (cyclomatic 28) vscode-fscript/extension.js
- Cyclomatic Complexity · IrArtifact.deserialize (cyclomatic 27) src/FScript.Compiler/IrArtifact.fs
- Cyclomatic Complexity · LirSimplification.optimize (cyclomatic 27) src/FScript.Compiler/LirSimplification.fs
- Cyclomatic Complexity · LirOptimization.optimize (cyclomatic 27) src/FScript.Compiler/Lir.fs
- Cyclomatic Complexity · LspSymbols.tryResolveLocalBindingFromRecordFieldAssignmentAtPosition (cyclomatic 27) src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs
- Cyclomatic Complexity · CompileOptions.resolve (cyclomatic 27) src/FScript/CompileOptions.fs
- Cyclomatic Complexity · Pretty.valueToString (cyclomatic 26) src/FScript.Language/Pretty.fs
- Cyclomatic Complexity · LspHandlers.handleTypeDefinition (cyclomatic 26) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs
- Cyclomatic Complexity · LspSymbols.lspTypeToString (cyclomatic 26) src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs
- Cyclomatic Complexity · Eval.valueToInterpolationString (cyclomatic 25) src/FScript.Language/Eval.fs
- Cyclomatic Complexity · AstJson.toJsonNodeInternal (cyclomatic 25) src/FScript.CSharpInterop/LanguageServer/AstJson.fs
- Cyclomatic Complexity · HostDecode.decodeXmlValue (cyclomatic 25) src/FScript.Runtime/Decode.fs
- Cyclomatic Complexity · DebuggerEntry.RunAdapterAsync (cyclomatic 24) src/FScript.DebugAdapter/DebuggerEntry.cs
- Cyclomatic Complexity · HirLowering.lower (cyclomatic 24) src/FScript.Compiler/HirLowering.fs
- Cyclomatic Complexity · LspHandlers.scanSemanticTokens (cyclomatic 24) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs
- Cyclomatic Complexity · Program.runRepl (cyclomatic 24) src/FScript/Program.fs
- Cyclomatic Complexity · Program.runOrdinaryCommand (cyclomatic 24) src/FScript/Program.fs
- Cyclomatic Complexity · sandbox.Sandbox (cyclomatic 24) website/src/pages/sandbox.tsx
- Cyclomatic Complexity · LirLowering.capturedReferences (cyclomatic 23) src/FScript.Compiler/Lir.fs
- Cyclomatic Complexity · LspSymbols.tryResolveTypeNameForQualifier (cyclomatic 23) src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs
- Cyclomatic Complexity · DotNetIlInlining.expand (cyclomatic 22) src/FScript.Backend.DotNet/DotNetIlInlining.fs
- Cyclomatic Complexity · LirMonomorphization.references (cyclomatic 22) src/FScript.Compiler/LirMonomorphization.fs
- Cyclomatic Complexity · TypeInfer.typeFromRef (cyclomatic 22) src/FScript.Language/TypeInfer.fs
- Cyclomatic Complexity · Lexer.readInterpolatedRaw (cyclomatic 22) src/FScript.Language/Lexer.fs
- Cyclomatic Complexity · DotNetPackaging.publish (cyclomatic 21) src/FScript.Backend.DotNet/DotNetPackaging.fs
- Cyclomatic Complexity · LspHandlers.handleHover (cyclomatic 21) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs
- Cyclomatic Complexity · JavaScript.validateRegistration (cyclomatic 21) src/FScript.JavaScript/Library.fs
- Cyclomatic Complexity · startFolderClient (cyclomatic 21) vscode-fscript/extension.js
- Cyclomatic Complexity · LirTupleElimination.optimize (cyclomatic 20) src/FScript.Compiler/LirTupleElimination.fs
- Cyclomatic Complexity · Eval.invokeTaskOperation (cyclomatic 20) src/FScript.Language/Eval.fs
- Cyclomatic Complexity · JavaScript.buildExternal (cyclomatic 20) src/FScript.JavaScript/Library.fs
Rebuild cost: about €51,000 · Estimate
| Cost to rebuild | €17,000 to €86,000, for 283 to 903 hours of work, about 0.4 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 54. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 31,107 lines of product code |
| Comment lines | The estimate prices 31,081 lines. Comment lines count towards the size of 31,107 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 — bounded-context dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Compiler.Hir | 2 Compiler.Lir | 3 Language | 4 LanguageServer.LspModel | 5 CSharpInterop.InteropServices | 6 Compiler | 7 Compiler.CSharpBackend | 8 Compiler.ClrBindings | 9 Compiler.DotNetCollectionFusion | 10 Compiler.DotNetCollectionRepresentations | 11 Compiler.DotNetIlInlining | 12 Compiler.DotNetOptimization | 13 Compiler.HirLowering | 14 Compiler.HirValidation | 15 Compiler.IrArtifact | 16 Compiler.LirAggregateElimination | 17 Compiler.LirCommonSubexpressions | 18 Compiler.LirEffects | 19 Compiler.LirLowering | 20 Compiler.LirMonomorphization | 21 Compiler.LirOptimization | 22 Language.TypeInfer | 23 LanguageServer.LspSymbols | 24 Runtime | 25 Compiler.CompilerExternCatalog | 26 Compiler.DotNetBackend | 27 Compiler.DotNetPackaging | 28 Compiler.LirInterpreter | 29 Language.Eval | 30 Language.ExportSignatures | 31 Language.TaskSharingAnalysis | 32 Runtime.DebugLaunch | 33 Runtime.EnvironmentLoader | 34 Runtime.FsExterns | 35 Runtime.HostCommon | 36 Runtime.Registry | 37 Language.Interactive | 38 Runtime.ScriptHost | 39 Runtime.TaskSharingContracts | 40 JavaScript |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Compiler.Hir | ||||||||||||||||||||||||||||||||||||||||
| 2 Compiler.Lir | ||||||||||||||||||||||||||||||||||||||||
| 3 Language | ||||||||||||||||||||||||||||||||||||||||
| 4 LanguageServer.LspModel | ||||||||||||||||||||||||||||||||||||||||
| 5 CSharpInterop.InteropServices | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 Compiler | 1 | 5 | ||||||||||||||||||||||||||||||||||||||
| 7 Compiler.CSharpBackend | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 Compiler.ClrBindings | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 Compiler.DotNetCollectionFusion | 2 | |||||||||||||||||||||||||||||||||||||||
| 10 Compiler.DotNetCollectionRepresentations | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 Compiler.DotNetIlInlining | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 Compiler.DotNetOptimization | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 Compiler.HirLowering | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 Compiler.HirValidation | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 Compiler.IrArtifact | 3 | |||||||||||||||||||||||||||||||||||||||
| 16 Compiler.LirAggregateElimination | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 Compiler.LirCommonSubexpressions | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 Compiler.LirEffects | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 Compiler.LirLowering | 3 | 3 | ||||||||||||||||||||||||||||||||||||||
| 20 Compiler.LirMonomorphization | 4 | |||||||||||||||||||||||||||||||||||||||
| 21 Compiler.LirOptimization | 2 | |||||||||||||||||||||||||||||||||||||||
| 22 Language.TypeInfer | 50 | |||||||||||||||||||||||||||||||||||||||
| 23 LanguageServer.LspSymbols | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 24 Runtime | 6 | |||||||||||||||||||||||||||||||||||||||
| 25 Compiler.CompilerExternCatalog | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 Compiler.DotNetBackend | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 Compiler.DotNetPackaging | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 Compiler.LirInterpreter | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 29 Language.Eval | 24 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 Language.ExportSignatures | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 Language.TaskSharingAnalysis | 3 | 3 | ||||||||||||||||||||||||||||||||||||||
| 32 Runtime.DebugLaunch | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 Runtime.EnvironmentLoader | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 34 Runtime.FsExterns | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 Runtime.HostCommon | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 Runtime.Registry | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 Language.Interactive | 7 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 38 Runtime.ScriptHost | 10 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 Runtime.TaskSharingContracts | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 JavaScript | 20 | 2 | 1 |
5→2 CSharpInterop.InteropServices uses Compiler.Lir✕
- Connections
- 1 pair of types, where a type in CSharpInterop.InteropServices uses a type in Compiler.Lir.
- The types involved
FScript.CSharpInterop.InteropServices.InteropServices→FScript.Compiler.Lir.Program
- Direction
- CSharpInterop.InteropServices uses Compiler.Lir, so a change to Compiler.Lir can break CSharpInterop.InteropServices, while a change to CSharpInterop.InteropServices can't break Compiler.Lir.
- Position
- Below the diagonal: CSharpInterop.InteropServices uses a module listed above it, which is the healthy direction.
6→1 Compiler uses Compiler.Hir✕
- Connections
- 1 pair of types, where a type in Compiler uses a type in Compiler.Hir.
- The types involved
FScript.Compiler.CompiledProgram→FScript.Compiler.Hir.Program
- Direction
- Compiler uses Compiler.Hir, so a change to Compiler.Hir can break Compiler, while a change to Compiler can't break Compiler.Hir.
- Position
- Below the diagonal: Compiler uses a module listed above it, which is the healthy direction.
6→2 Compiler uses Compiler.Lir✕
- Connections
- 5 pairs of types, where a type in Compiler uses a type in Compiler.Lir.
- The types involved
FScript.Compiler.CompileInput→FScript.Compiler.Lir.ProgramFScript.Compiler.CompiledProgram→FScript.Compiler.Lir.ProgramFScript.Compiler.LirValue→FScript.Compiler.Lir.ExpressionFScript.Compiler.LirValue→FScript.Compiler.Lir.SymbolIdFScript.Compiler.LoadedProgram→FScript.Compiler.Lir.Program
- Direction
- Compiler uses Compiler.Lir, so a change to Compiler.Lir can break Compiler, while a change to Compiler can't break Compiler.Lir.
- Position
- Below the diagonal: Compiler uses a module listed above it, which is the healthy direction.
7→2 Compiler.CSharpBackend uses Compiler.Lir✕
- Connections
- 1 pair of types, where a type in Compiler.CSharpBackend uses a type in Compiler.Lir.
- The types involved
FScript.Compiler.CSharpBackend.CSharpBackend→FScript.Compiler.Lir.Program
- Direction
- Compiler.CSharpBackend uses Compiler.Lir, so a change to Compiler.Lir can break Compiler.CSharpBackend, while a change to Compiler.CSharpBackend can't break Compiler.Lir.
- Position
- Below the diagonal: Compiler.CSharpBackend uses a module listed above it, which is the healthy direction.
8→2 Compiler.ClrBindings uses Compiler.Lir✕
- Connections
- 1 pair of types, where a type in Compiler.ClrBindings uses a type in Compiler.Lir.
- The types involved
FScript.Compiler.ClrBindings.ClrBindings→FScript.Compiler.Lir.Program
- Direction
- Compiler.ClrBindings uses Compiler.Lir, so a change to Compiler.Lir can break Compiler.ClrBindings, while a change to Compiler.ClrBindings can't break Compiler.Lir.
- Position
- Below the diagonal: Compiler.ClrBindings uses a module listed above it, which is the healthy direction.
9→2 Compiler.DotNetCollectionFusion uses Compiler.Lir✕
- Connections
- 2 pairs of types, where a type in Compiler.DotNetCollectionFusion uses a type in Compiler.Lir.
- The types involved
FScript.Compiler.DotNetCollectionFusion.DotNetCollectionFusion→FScript.Compiler.Lir.ProgramFScript.Compiler.DotNetCollectionFusion.Stage→FScript.Compiler.Lir.Expression
- Direction
- Compiler.DotNetCollectionFusion uses Compiler.Lir, so a change to Compiler.Lir can break Compiler.DotNetCollectionFusion, while a change to Compiler.DotNetCollectionFusion can't break Compiler.Lir.
- Position
- Below the diagonal: Compiler.DotNetCollectionFusion uses a module listed above it, which is the healthy direction.
10→2 Compiler.DotNetCollectionRepresentations uses Compiler.Lir✕
- Connections
- 1 pair of types, where a type in Compiler.DotNetCollectionRepresentations uses a type in Compiler.Lir.
- The types involved
FScript.Compiler.DotNetCollectionRepresentations.DotNetCollectionRepresentations→FScript.Compiler.Lir.Program
- Direction
- Compiler.DotNetCollectionRepresentations uses Compiler.Lir, so a change to Compiler.Lir can break Compiler.DotNetCollectionRepresentations, while a change to Compiler.DotNetCollectionRepresentations can't break Compiler.Lir.
- Position
- Below the diagonal: Compiler.DotNetCollectionRepresentations uses a module listed above it, which is the healthy direction.
11→2 Compiler.DotNetIlInlining uses Compiler.Lir✕
- Connections
- 1 pair of types, where a type in Compiler.DotNetIlInlining uses a type in Compiler.Lir.
- The types involved
FScript.Compiler.DotNetIlInlining.DotNetIlInlining→FScript.Compiler.Lir.Program
- Direction
- Compiler.DotNetIlInlining uses Compiler.Lir, so a change to Compiler.Lir can break Compiler.DotNetIlInlining, while a change to Compiler.DotNetIlInlining can't break Compiler.Lir.
- Position
- Below the diagonal: Compiler.DotNetIlInlining uses a module listed above it, which is the healthy direction.
12→2 Compiler.DotNetOptimization uses Compiler.Lir✕
- Connections
- 2 pairs of types, where a type in Compiler.DotNetOptimization uses a type in Compiler.Lir.
- The types involved
FScript.Compiler.DotNetOptimization.DotNetOptimization→FScript.Compiler.Lir.ExpressionFScript.Compiler.DotNetOptimization.DotNetOptimization→FScript.Compiler.Lir.Program
- Direction
- Compiler.DotNetOptimization uses Compiler.Lir, so a change to Compiler.Lir can break Compiler.DotNetOptimization, while a change to Compiler.DotNetOptimization can't break Compiler.Lir.
- Position
- Below the diagonal: Compiler.DotNetOptimization uses a module listed above it, which is the healthy direction.
13→1 Compiler.HirLowering uses Compiler.Hir✕
- Connections
- 1 pair of types, where a type in Compiler.HirLowering uses a type in Compiler.Hir.
- The types involved
FScript.Compiler.HirLowering.HirLowering→FScript.Compiler.Hir.Expression
- Direction
- Compiler.HirLowering uses Compiler.Hir, so a change to Compiler.Hir can break Compiler.HirLowering, while a change to Compiler.HirLowering can't break Compiler.Hir.
- Position
- Below the diagonal: Compiler.HirLowering uses a module listed above it, which is the healthy direction.
14→1 Compiler.HirValidation uses Compiler.Hir✕
- Connections
- 1 pair of types, where a type in Compiler.HirValidation uses a type in Compiler.Hir.
- The types involved
FScript.Compiler.HirValidation.HirValidation→FScript.Compiler.Hir.Program
- Direction
- Compiler.HirValidation uses Compiler.Hir, so a change to Compiler.Hir can break Compiler.HirValidation, while a change to Compiler.HirValidation can't break Compiler.Hir.
- Position
- Below the diagonal: Compiler.HirValidation uses a module listed above it, which is the healthy direction.
15→2 Compiler.IrArtifact uses Compiler.Lir✕
- Connections
- 3 pairs of types, where a type in Compiler.IrArtifact uses a type in Compiler.Lir.
- The types involved
FScript.Compiler.IrArtifact.IrArtifact→FScript.Compiler.Lir.ExpressionFScript.Compiler.IrArtifact.IrArtifact→FScript.Compiler.Lir.PatternPlanFScript.Compiler.IrArtifact.IrArtifact→FScript.Compiler.Lir.Program
- Direction
- Compiler.IrArtifact uses Compiler.Lir, so a change to Compiler.Lir can break Compiler.IrArtifact, while a change to Compiler.IrArtifact can't break Compiler.Lir.
- Position
- Below the diagonal: Compiler.IrArtifact uses a module listed above it, which is the healthy direction.
16→2 Compiler.LirAggregateElimination uses Compiler.Lir✕
- Connections
- 1 pair of types, where a type in Compiler.LirAggregateElimination uses a type in Compiler.Lir.
- The types involved
FScript.Compiler.LirAggregateElimination.LirAggregateElimination→FScript.Compiler.Lir.Program
- Direction
- Compiler.LirAggregateElimination uses Compiler.Lir, so a change to Compiler.Lir can break Compiler.LirAggregateElimination, while a change to Compiler.LirAggregateElimination can't break Compiler.Lir.
- Position
- Below the diagonal: Compiler.LirAggregateElimination uses a module listed above it, which is the healthy direction.
17→2 Compiler.LirCommonSubexpressions uses Compiler.Lir✕
- Connections
- 1 pair of types, where a type in Compiler.LirCommonSubexpressions uses a type in Compiler.Lir.
- The types involved
FScript.Compiler.LirCommonSubexpressions.LirCommonSubexpressions→FScript.Compiler.Lir.Program
- Direction
- Compiler.LirCommonSubexpressions uses Compiler.Lir, so a change to Compiler.Lir can break Compiler.LirCommonSubexpressions, while a change to Compiler.LirCommonSubexpressions can't break Compiler.Lir.
- Position
- Below the diagonal: Compiler.LirCommonSubexpressions uses a module listed above it, which is the healthy direction.
18→2 Compiler.LirEffects uses Compiler.Lir✕
- Connections
- 1 pair of types, where a type in Compiler.LirEffects uses a type in Compiler.Lir.
- The types involved
FScript.Compiler.LirEffects.LirEffects→FScript.Compiler.Lir.Program
- Direction
- Compiler.LirEffects uses Compiler.Lir, so a change to Compiler.Lir can break Compiler.LirEffects, while a change to Compiler.LirEffects can't break Compiler.Lir.
- Position
- Below the diagonal: Compiler.LirEffects uses a module listed above it, which is the healthy direction.
19→1 Compiler.LirLowering uses Compiler.Hir✕
- Connections
- 3 pairs of types, where a type in Compiler.LirLowering uses a type in Compiler.Hir.
- The types involved
FScript.Compiler.LirLowering.LirLowering→FScript.Compiler.Hir.ExpressionFScript.Compiler.LirLowering.LirLowering→FScript.Compiler.Hir.PatternFScript.Compiler.LirLowering.LirLowering→FScript.Compiler.Hir.Program
- Direction
- Compiler.LirLowering uses Compiler.Hir, so a change to Compiler.Hir can break Compiler.LirLowering, while a change to Compiler.LirLowering can't break Compiler.Hir.
- Position
- Below the diagonal: Compiler.LirLowering uses a module listed above it, which is the healthy direction.
19→2 Compiler.LirLowering uses Compiler.Lir✕
- Connections
- 3 pairs of types, where a type in Compiler.LirLowering uses a type in Compiler.Lir.
- The types involved
FScript.Compiler.LirLowering.LirLowering→FScript.Compiler.Lir.ExpressionFScript.Compiler.LirLowering.LirLowering→FScript.Compiler.Lir.PatternPlanFScript.Compiler.LirLowering.LirLowering→FScript.Compiler.Lir.Program
- Direction
- Compiler.LirLowering uses Compiler.Lir, so a change to Compiler.Lir can break Compiler.LirLowering, while a change to Compiler.LirLowering can't break Compiler.Lir.
- Position
- Below the diagonal: Compiler.LirLowering uses a module listed above it, which is the healthy direction.
20→2 Compiler.LirMonomorphization uses Compiler.Lir✕
- Connections
- 4 pairs of types, where a type in Compiler.LirMonomorphization uses a type in Compiler.Lir.
- The types involved
FScript.Compiler.LirMonomorphization.LirMonomorphization→FScript.Compiler.Lir.ExpressionFScript.Compiler.LirMonomorphization.LirMonomorphization→FScript.Compiler.Lir.PatternPlanFScript.Compiler.LirMonomorphization.LirMonomorphization→FScript.Compiler.Lir.ProgramFScript.Compiler.LirMonomorphization.State→FScript.Compiler.Lir.Program
- Direction
- Compiler.LirMonomorphization uses Compiler.Lir, so a change to Compiler.Lir can break Compiler.LirMonomorphization, while a change to Compiler.LirMonomorphization can't break Compiler.Lir.
- Position
- Below the diagonal: Compiler.LirMonomorphization uses a module listed above it, which is the healthy direction.
21→2 Compiler.LirOptimization uses Compiler.Lir✕
- Connections
- 2 pairs of types, where a type in Compiler.LirOptimization uses a type in Compiler.Lir.
- The types involved
FScript.Compiler.LirOptimization.LirOptimization→FScript.Compiler.Lir.ExpressionFScript.Compiler.LirOptimization.LirOptimization→FScript.Compiler.Lir.Program
- Direction
- Compiler.LirOptimization uses Compiler.Lir, so a change to Compiler.Lir can break Compiler.LirOptimization, while a change to Compiler.LirOptimization can't break Compiler.Lir.
- Position
- Below the diagonal: Compiler.LirOptimization uses a module listed above it, which is the healthy direction.
22→3 Language.TypeInfer uses Language✕
- Connections
- 50 pairs of types, where a type in Language.TypeInfer uses a type in Language. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
FScript.Language.TypeInfer.ConstructorSig→FScript.Language.TypeFScript.Language.TypeInfer.LocalVariableTypeCapture→FScript.Language.SpanFScript.Language.TypeInfer.LocalVariableTypeCapture→FScript.Language.TypeFScript.Language.TypeInfer.LocalVariableTypeInfo→FScript.Language.SpanFScript.Language.TypeInfer.LocalVariableTypeInfo→FScript.Language.TypeFScript.Language.TypeInfer.RecordCoercionEvidence→FScript.Language.TypeFScript.Language.TypeInfer.ResolvedBackendImport→FScript.Language.SpanFScript.Language.TypeInfer.ResolvedBinding→FScript.Language.SpanFScript.Language.TypeInfer.ResolvedBinding→FScript.Language.TypeFScript.Language.TypeInfer.ResolvedExport→FScript.Language.SpanFScript.Language.TypeInfer.ResolvedExpression→FScript.Language.SpanFScript.Language.TypeInfer.ResolvedExpression→FScript.Language.TypeFScript.Language.TypeInfer.ResolvedExpressionNode→FScript.Language.TypeFScript.Language.TypeInfer.ResolvedExpressionType→FScript.Language.ExprFScript.Language.TypeInfer.ResolvedExpressionType→FScript.Language.SpanFScript.Language.TypeInfer.ResolvedExpressionType→FScript.Language.TypeFScript.Language.TypeInfer.ResolvedImportedDeclaration→FScript.Language.SchemeFScript.Language.TypeInfer.ResolvedMatchCase→FScript.Language.SpanFScript.Language.TypeInfer.ResolvedPattern→FScript.Language.SpanFScript.Language.TypeInfer.ResolvedPattern→FScript.Language.TypeFScript.Language.TypeInfer.ResolvedPatternNode→FScript.Language.TypeFScript.Language.TypeInfer.ResolvedProgram→FScript.Language.PurityContractsFScript.Language.TypeInfer.ResolvedStatement→FScript.Language.AttributeFScript.Language.TypeInfer.ResolvedStatement→FScript.Language.SpanFScript.Language.TypeInfer.ResolvedSymbol→FScript.Language.Scheme
- Direction
- Language.TypeInfer uses Language, so a change to Language can break Language.TypeInfer, while a change to Language.TypeInfer can't break Language.
- Position
- Below the diagonal: Language.TypeInfer uses a module listed above it, which is the healthy direction.
23→1 LanguageServer.LspSymbols uses Compiler.Hir✕
- Connections
- 1 pair of types, where a type in LanguageServer.LspSymbols uses a type in Compiler.Hir.
- The types involved
FScript.LanguageServer.LspSymbols.LspSymbols→FScript.Compiler.Hir.Pattern
- Direction
- LanguageServer.LspSymbols uses Compiler.Hir, so a change to Compiler.Hir can break LanguageServer.LspSymbols, while a change to LanguageServer.LspSymbols can't break Compiler.Hir.
- Position
- Below the diagonal: LanguageServer.LspSymbols uses a module listed above it, which is the healthy direction.
23→2 LanguageServer.LspSymbols uses Compiler.Lir✕
- Connections
- 1 pair of types, where a type in LanguageServer.LspSymbols uses a type in Compiler.Lir.
- The types involved
FScript.LanguageServer.LspSymbols.LspSymbols→FScript.Compiler.Lir.Program
- Direction
- LanguageServer.LspSymbols uses Compiler.Lir, so a change to Compiler.Lir can break LanguageServer.LspSymbols, while a change to LanguageServer.LspSymbols can't break Compiler.Lir.
- Position
- Below the diagonal: LanguageServer.LspSymbols uses a module listed above it, which is the healthy direction.
23→4 LanguageServer.LspSymbols uses LanguageServer.LspModel✕
- Connections
- 2 pairs of types, where a type in LanguageServer.LspSymbols uses a type in LanguageServer.LspModel.
- The types involved
FScript.LanguageServer.LspSymbols.LspSymbols→FScript.LanguageServer.LspModel.DocumentStateFScript.LanguageServer.LspSymbols.LspSymbols→FScript.LanguageServer.LspModel.TopLevelSymbol
- Direction
- LanguageServer.LspSymbols uses LanguageServer.LspModel, so a change to LanguageServer.LspModel can break LanguageServer.LspSymbols, while a change to LanguageServer.LspSymbols can't break LanguageServer.LspModel.
- Position
- Below the diagonal: LanguageServer.LspSymbols uses a module listed above it, which is the healthy direction.
24→3 Runtime uses Language✕
- Connections
- 6 pairs of types, where a type in Runtime uses a type in Language.
- The types involved
FScript.Runtime.DebugSession→FScript.Language.ExtensionRegistrationFScript.Runtime.DebugSession→FScript.Language.StmtFScript.Runtime.Frame→FScript.Language.SpanFScript.Runtime.Frame→FScript.Language.ValueFScript.Runtime.HostContext→FScript.Language.HostPermissionsFScript.Runtime.LoadedEnvironment→FScript.Language.ExtensionRegistration
- Direction
- Runtime uses Language, so a change to Language can break Runtime, while a change to Runtime can't break Language.
- Position
- Below the diagonal: Runtime uses a module listed above it, which is the healthy direction.
25→6 Compiler.CompilerExternCatalog uses Compiler✕
- Connections
- 1 pair of types, where a type in Compiler.CompilerExternCatalog uses a type in Compiler.
- The types involved
FScript.Compiler.CompilerExternCatalog.CompilerExternCatalog→FScript.Compiler.CompilerExtern
- Direction
- Compiler.CompilerExternCatalog uses Compiler, so a change to Compiler can break Compiler.CompilerExternCatalog, while a change to Compiler.CompilerExternCatalog can't break Compiler.
- Position
- Below the diagonal: Compiler.CompilerExternCatalog uses a module listed above it, which is the healthy direction.
26→2 Compiler.DotNetBackend uses Compiler.Lir✕
- Connections
- 1 pair of types, where a type in Compiler.DotNetBackend uses a type in Compiler.Lir.
- The types involved
FScript.Compiler.DotNetBackend.DotNetBackend→FScript.Compiler.Lir.Program
- Direction
- Compiler.DotNetBackend uses Compiler.Lir, so a change to Compiler.Lir can break Compiler.DotNetBackend, while a change to Compiler.DotNetBackend can't break Compiler.Lir.
- Position
- Below the diagonal: Compiler.DotNetBackend uses a module listed above it, which is the healthy direction.
26→6 Compiler.DotNetBackend uses Compiler✕
- Connections
- 1 pair of types, where a type in Compiler.DotNetBackend uses a type in Compiler.
- The types involved
FScript.Compiler.DotNetBackend.DotNetBackend→FScript.Compiler.DotNetOptions
- Direction
- Compiler.DotNetBackend uses Compiler, so a change to Compiler can break Compiler.DotNetBackend, while a change to Compiler.DotNetBackend can't break Compiler.
- Position
- Below the diagonal: Compiler.DotNetBackend uses a module listed above it, which is the healthy direction.
27→6 Compiler.DotNetPackaging uses Compiler✕
- Connections
- 1 pair of types, where a type in Compiler.DotNetPackaging uses a type in Compiler.
- The types involved
FScript.Compiler.DotNetPackaging.DotNetPackaging→FScript.Compiler.DotNetOptions
- Direction
- Compiler.DotNetPackaging uses Compiler, so a change to Compiler can break Compiler.DotNetPackaging, while a change to Compiler.DotNetPackaging can't break Compiler.
- Position
- Below the diagonal: Compiler.DotNetPackaging uses a module listed above it, which is the healthy direction.
28→2 Compiler.LirInterpreter uses Compiler.Lir✕
- Connections
- 3 pairs of types, where a type in Compiler.LirInterpreter uses a type in Compiler.Lir.
- The types involved
FScript.Compiler.LirInterpreter.LirInterpreter→FScript.Compiler.Lir.ExpressionFScript.Compiler.LirInterpreter.LirInterpreter→FScript.Compiler.Lir.PatternPlanFScript.Compiler.LirInterpreter.LirInterpreter→FScript.Compiler.Lir.Program
- Direction
- Compiler.LirInterpreter uses Compiler.Lir, so a change to Compiler.Lir can break Compiler.LirInterpreter, while a change to Compiler.LirInterpreter can't break Compiler.Lir.
- Position
- Below the diagonal: Compiler.LirInterpreter uses a module listed above it, which is the healthy direction.
28→6 Compiler.LirInterpreter uses Compiler✕
- Connections
- 2 pairs of types, where a type in Compiler.LirInterpreter uses a type in Compiler.
- The types involved
FScript.Compiler.LirInterpreter.LirInterpreter→FScript.Compiler.InterpreterContextFScript.Compiler.LirInterpreter.LirInterpreter→FScript.Compiler.LoadedProgram
- Direction
- Compiler.LirInterpreter uses Compiler, so a change to Compiler can break Compiler.LirInterpreter, while a change to Compiler.LirInterpreter can't break Compiler.
- Position
- Below the diagonal: Compiler.LirInterpreter uses a module listed above it, which is the healthy direction.
29→3 Language.Eval uses Language✕
- Connections
- 24 pairs of types, where a type in Language.Eval uses a type in Language.
- The types involved
FScript.Language.Eval.Eval→FScript.Language.EvalErrorFScript.Language.Eval.Eval→FScript.Language.Execution`1FScript.Language.Eval.Eval→FScript.Language.ExprFScript.Language.Eval.Eval→FScript.Language.ExtensionRegistrationFScript.Language.Eval.Eval→FScript.Language.ExternalCallContextFScript.Language.Eval.Eval→FScript.Language.ExternalFunctionFScript.Language.Eval.Eval→FScript.Language.HostPermissionsFScript.Language.Eval.Eval→FScript.Language.IDebugObserverFScript.Language.Eval.Eval→FScript.Language.LiteralFScript.Language.Eval.Eval→FScript.Language.MapKeyFScript.Language.Eval.Eval→FScript.Language.PatternFScript.Language.Eval.Eval→FScript.Language.SpanFScript.Language.Eval.Eval→FScript.Language.TaskHandleFScript.Language.Eval.Eval→FScript.Language.TaskOutcomeFScript.Language.Eval.Eval→FScript.Language.TypeFScript.Language.Eval.Eval→FScript.Language.TypeRefFScript.Language.Eval.Eval→FScript.Language.ValueFScript.Language.Eval.InvocationResult→FScript.Language.ValueFScript.Language.Eval.ProgramState→FScript.Language.HostPermissionsFScript.Language.Eval.ProgramState→FScript.Language.TypeFScript.Language.Eval.ProgramState→FScript.Language.ValueFScript.Language.Eval.RuntimeState→FScript.Language.HostPermissionsFScript.Language.Eval.RuntimeState→FScript.Language.IDebugObserverFScript.Language.Eval.RuntimeState→FScript.Language.TaskHandle
- Direction
- Language.Eval uses Language, so a change to Language can break Language.Eval, while a change to Language.Eval can't break Language.
- Position
- Below the diagonal: Language.Eval uses a module listed above it, which is the healthy direction.
29→22 Language.Eval uses Language.TypeInfer✕
- Connections
- 1 pair of types, where a type in Language.Eval uses a type in Language.TypeInfer.
- The types involved
FScript.Language.Eval.Eval→FScript.Language.TypeInfer.TypedStmt
- Direction
- Language.Eval uses Language.TypeInfer, so a change to Language.TypeInfer can break Language.Eval, while a change to Language.Eval can't break Language.TypeInfer.
- Position
- Below the diagonal: Language.Eval uses a module listed above it, which is the healthy direction.
30→3 Language.ExportSignatures uses Language✕
- Connections
- 3 pairs of types, where a type in Language.ExportSignatures uses a type in Language.
- The types involved
FScript.Language.ExportSignatures.ExportSignatures→FScript.Language.ExprFScript.Language.ExportSignatures.ExportSignatures→FScript.Language.TypeFScript.Language.ExportSignatures.ExportedFunctionSignature→FScript.Language.Type
- Direction
- Language.ExportSignatures uses Language, so a change to Language can break Language.ExportSignatures, while a change to Language.ExportSignatures can't break Language.
- Position
- Below the diagonal: Language.ExportSignatures uses a module listed above it, which is the healthy direction.
30→22 Language.ExportSignatures uses Language.TypeInfer✕
- Connections
- 1 pair of types, where a type in Language.ExportSignatures uses a type in Language.TypeInfer.
- The types involved
FScript.Language.ExportSignatures.ExportSignatures→FScript.Language.TypeInfer.TypedStmt
- Direction
- Language.ExportSignatures uses Language.TypeInfer, so a change to Language.TypeInfer can break Language.ExportSignatures, while a change to Language.ExportSignatures can't break Language.TypeInfer.
- Position
- Below the diagonal: Language.ExportSignatures uses a module listed above it, which is the healthy direction.
31→3 Language.TaskSharingAnalysis uses Language✕
- Connections
- 3 pairs of types, where a type in Language.TaskSharingAnalysis uses a type in Language.
- The types involved
FScript.Language.TaskSharingAnalysis.Callable→FScript.Language.TypeFScript.Language.TaskSharingAnalysis.Diagnostic→FScript.Language.SpanFScript.Language.TaskSharingAnalysis.TaskSharingAnalysis→FScript.Language.ExtensionRegistration
- Direction
- Language.TaskSharingAnalysis uses Language, so a change to Language can break Language.TaskSharingAnalysis, while a change to Language.TaskSharingAnalysis can't break Language.
- Position
- Below the diagonal: Language.TaskSharingAnalysis uses a module listed above it, which is the healthy direction.
31→22 Language.TaskSharingAnalysis uses Language.TypeInfer✕
- Connections
- 3 pairs of types, where a type in Language.TaskSharingAnalysis uses a type in Language.TypeInfer.
- The types involved
FScript.Language.TaskSharingAnalysis.Callable→FScript.Language.TypeInfer.ResolvedBindingFScript.Language.TaskSharingAnalysis.Callable→FScript.Language.TypeInfer.ResolvedExpressionFScript.Language.TaskSharingAnalysis.TaskSharingAnalysis→FScript.Language.TypeInfer.ResolvedProgram
- Direction
- Language.TaskSharingAnalysis uses Language.TypeInfer, so a change to Language.TypeInfer can break Language.TaskSharingAnalysis, while a change to Language.TaskSharingAnalysis can't break Language.TypeInfer.
- Position
- Below the diagonal: Language.TaskSharingAnalysis uses a module listed above it, which is the healthy direction.
32→3 Runtime.DebugLaunch uses Language✕
- Connections
- 1 pair of types, where a type in Runtime.DebugLaunch uses a type in Language.
- The types involved
FScript.Runtime.DebugLaunch.DebugLaunch→FScript.Language.HostPermissions
- Direction
- Runtime.DebugLaunch uses Language, so a change to Language can break Runtime.DebugLaunch, while a change to Runtime.DebugLaunch can't break Language.
- Position
- Below the diagonal: Runtime.DebugLaunch uses a module listed above it, which is the healthy direction.
32→24 Runtime.DebugLaunch uses Runtime✕
- Connections
- 1 pair of types, where a type in Runtime.DebugLaunch uses a type in Runtime.
- The types involved
FScript.Runtime.DebugLaunch.DebugLaunch→FScript.Runtime.DebugSession
- Direction
- Runtime.DebugLaunch uses Runtime, so a change to Runtime can break Runtime.DebugLaunch, while a change to Runtime.DebugLaunch can't break Runtime.
- Position
- Below the diagonal: Runtime.DebugLaunch uses a module listed above it, which is the healthy direction.
33→3 Runtime.EnvironmentLoader uses Language✕
- Connections
- 2 pairs of types, where a type in Runtime.EnvironmentLoader uses a type in Language.
- The types involved
FScript.Runtime.EnvironmentLoader.EnvironmentLoader→FScript.Language.ExtensionRegistrationFScript.Runtime.EnvironmentLoader.EnvironmentLoader→FScript.Language.HostPermissions
- Direction
- Runtime.EnvironmentLoader uses Language, so a change to Language can break Runtime.EnvironmentLoader, while a change to Runtime.EnvironmentLoader can't break Language.
- Position
- Below the diagonal: Runtime.EnvironmentLoader uses a module listed above it, which is the healthy direction.
33→24 Runtime.EnvironmentLoader uses Runtime✕
- Connections
- 2 pairs of types, where a type in Runtime.EnvironmentLoader uses a type in Runtime.
- The types involved
FScript.Runtime.EnvironmentLoader.EnvironmentLoader→FScript.Runtime.EnvironmentSettingsFScript.Runtime.EnvironmentLoader.EnvironmentLoader→FScript.Runtime.LoadedEnvironment
- Direction
- Runtime.EnvironmentLoader uses Runtime, so a change to Runtime can break Runtime.EnvironmentLoader, while a change to Runtime.EnvironmentLoader can't break Runtime.
- Position
- Below the diagonal: Runtime.EnvironmentLoader uses a module listed above it, which is the healthy direction.
34→3 Runtime.FsExterns uses Language✕
- Connections
- 1 pair of types, where a type in Runtime.FsExterns uses a type in Language.
- The types involved
FScript.Runtime.FsExterns.FsExterns→FScript.Language.ExternalFunction
- Direction
- Runtime.FsExterns uses Language, so a change to Language can break Runtime.FsExterns, while a change to Runtime.FsExterns can't break Language.
- Position
- Below the diagonal: Runtime.FsExterns uses a module listed above it, which is the healthy direction.
34→24 Runtime.FsExterns uses Runtime✕
- Connections
- 1 pair of types, where a type in Runtime.FsExterns uses a type in Runtime.
- The types involved
FScript.Runtime.FsExterns.FsExterns→FScript.Runtime.HostContext
- Direction
- Runtime.FsExterns uses Runtime, so a change to Runtime can break Runtime.FsExterns, while a change to Runtime.FsExterns can't break Runtime.
- Position
- Below the diagonal: Runtime.FsExterns uses a module listed above it, which is the healthy direction.
35→3 Runtime.HostCommon uses Language✕
- Connections
- 2 pairs of types, where a type in Runtime.HostCommon uses a type in Language.
- The types involved
FScript.Runtime.HostCommon.HostCommon→FScript.Language.SpanFScript.Runtime.HostCommon.HostCommon→FScript.Language.Value
- Direction
- Runtime.HostCommon uses Language, so a change to Language can break Runtime.HostCommon, while a change to Runtime.HostCommon can't break Language.
- Position
- Below the diagonal: Runtime.HostCommon uses a module listed above it, which is the healthy direction.
35→24 Runtime.HostCommon uses Runtime✕
- Connections
- 1 pair of types, where a type in Runtime.HostCommon uses a type in Runtime.
- The types involved
FScript.Runtime.HostCommon.HostCommon→FScript.Runtime.HostContext
- Direction
- Runtime.HostCommon uses Runtime, so a change to Runtime can break Runtime.HostCommon, while a change to Runtime.HostCommon can't break Runtime.
- Position
- Below the diagonal: Runtime.HostCommon uses a module listed above it, which is the healthy direction.
36→3 Runtime.Registry uses Language✕
- Connections
- 2 pairs of types, where a type in Runtime.Registry uses a type in Language.
- The types involved
FScript.Runtime.Registry.Registry→FScript.Language.ExtensionRegistrationFScript.Runtime.Registry.Registry→FScript.Language.ExternalFunction
- Direction
- Runtime.Registry uses Language, so a change to Language can break Runtime.Registry, while a change to Runtime.Registry can't break Language.
- Position
- Below the diagonal: Runtime.Registry uses a module listed above it, which is the healthy direction.
36→24 Runtime.Registry uses Runtime✕
- Connections
- 1 pair of types, where a type in Runtime.Registry uses a type in Runtime.
- The types involved
FScript.Runtime.Registry.Registry→FScript.Runtime.HostContext
- Direction
- Runtime.Registry uses Runtime, so a change to Runtime can break Runtime.Registry, while a change to Runtime.Registry can't break Runtime.
- Position
- Below the diagonal: Runtime.Registry uses a module listed above it, which is the healthy direction.
37→3 Language.Interactive uses Language✕
- Connections
- 7 pairs of types, where a type in Language.Interactive uses a type in Language.
- The types involved
FScript.Language.Interactive.Interactive→FScript.Language.ExtensionRegistrationFScript.Language.Interactive.Interactive→FScript.Language.ExternalFunctionFScript.Language.Interactive.Interactive→FScript.Language.StmtFScript.Language.Interactive.Interactive→FScript.Language.TypeFScript.Language.Interactive.Session→FScript.Language.ExtensionRegistrationFScript.Language.Interactive.Session→FScript.Language.ExternalFunctionFScript.Language.Interactive.Session→FScript.Language.Stmt
- Direction
- Language.Interactive uses Language, so a change to Language can break Language.Interactive, while a change to Language.Interactive can't break Language.
- Position
- Below the diagonal: Language.Interactive uses a module listed above it, which is the healthy direction.
37→22 Language.Interactive uses Language.TypeInfer✕
- Connections
- 2 pairs of types, where a type in Language.Interactive uses a type in Language.TypeInfer.
- The types involved
FScript.Language.Interactive.Interactive→FScript.Language.TypeInfer.TypedStmtFScript.Language.Interactive.Submission→FScript.Language.TypeInfer.TypedStmt
- Direction
- Language.Interactive uses Language.TypeInfer, so a change to Language.TypeInfer can break Language.Interactive, while a change to Language.Interactive can't break Language.TypeInfer.
- Position
- Below the diagonal: Language.Interactive uses a module listed above it, which is the healthy direction.
37→29 Language.Interactive uses Language.Eval✕
- Connections
- 2 pairs of types, where a type in Language.Interactive uses a type in Language.Eval.
- The types involved
FScript.Language.Interactive.Session→FScript.Language.Eval.ProgramStateFScript.Language.Interactive.Submission→FScript.Language.Eval.ProgramState
- Direction
- Language.Interactive uses Language.Eval, so a change to Language.Eval can break Language.Interactive, while a change to Language.Interactive can't break Language.Eval.
- Position
- Below the diagonal: Language.Interactive uses a module listed above it, which is the healthy direction.
38→3 Runtime.ScriptHost uses Language✕
- Connections
- 10 pairs of types, where a type in Runtime.ScriptHost uses a type in Language.
- The types involved
FScript.Runtime.ScriptHost.FunctionSignature→FScript.Language.TypeFScript.Runtime.ScriptHost.LoadedScript→FScript.Language.HostPermissionsFScript.Runtime.ScriptHost.LoadedScript→FScript.Language.TypeFScript.Runtime.ScriptHost.LoadedScript→FScript.Language.ValueFScript.Runtime.ScriptHost.ScriptHost→FScript.Language.ExtensionRegistrationFScript.Runtime.ScriptHost.ScriptHost→FScript.Language.ExternalFunctionFScript.Runtime.ScriptHost.ScriptHost→FScript.Language.HostPermissionsFScript.Runtime.ScriptHost.ScriptHost→FScript.Language.PurityContractsFScript.Runtime.ScriptHost.ScriptHost→FScript.Language.StmtFScript.Runtime.ScriptHost.ScriptHost→FScript.Language.Value
- Direction
- Runtime.ScriptHost uses Language, so a change to Language can break Runtime.ScriptHost, while a change to Runtime.ScriptHost can't break Language.
- Position
- Below the diagonal: Runtime.ScriptHost uses a module listed above it, which is the healthy direction.
38→22 Runtime.ScriptHost uses Language.TypeInfer✕
- Connections
- 1 pair of types, where a type in Runtime.ScriptHost uses a type in Language.TypeInfer.
- The types involved
FScript.Runtime.ScriptHost.ScriptHost→FScript.Language.TypeInfer.TypedStmt
- Direction
- Runtime.ScriptHost uses Language.TypeInfer, so a change to Language.TypeInfer can break Runtime.ScriptHost, while a change to Runtime.ScriptHost can't break Language.TypeInfer.
- Position
- Below the diagonal: Runtime.ScriptHost uses a module listed above it, which is the healthy direction.
38→29 Runtime.ScriptHost uses Language.Eval✕
- Connections
- 1 pair of types, where a type in Runtime.ScriptHost uses a type in Language.Eval.
- The types involved
FScript.Runtime.ScriptHost.ScriptHost→FScript.Language.Eval.InvocationResult
- Direction
- Runtime.ScriptHost uses Language.Eval, so a change to Language.Eval can break Runtime.ScriptHost, while a change to Runtime.ScriptHost can't break Language.Eval.
- Position
- Below the diagonal: Runtime.ScriptHost uses a module listed above it, which is the healthy direction.
38→31 Runtime.ScriptHost uses Language.TaskSharingAnalysis✕
- Connections
- 1 pair of types, where a type in Runtime.ScriptHost uses a type in Language.TaskSharingAnalysis.
- The types involved
FScript.Runtime.ScriptHost.ScriptHost→FScript.Language.TaskSharingAnalysis.Options
- Direction
- Runtime.ScriptHost uses Language.TaskSharingAnalysis, so a change to Language.TaskSharingAnalysis can break Runtime.ScriptHost, while a change to Runtime.ScriptHost can't break Language.TaskSharingAnalysis.
- Position
- Below the diagonal: Runtime.ScriptHost uses a module listed above it, which is the healthy direction.
39→3 Runtime.TaskSharingContracts uses Language✕
- Connections
- 1 pair of types, where a type in Runtime.TaskSharingContracts uses a type in Language.
- The types involved
FScript.Runtime.TaskSharingContracts.TaskSharingContracts→FScript.Language.ExtensionRegistration
- Direction
- Runtime.TaskSharingContracts uses Language, so a change to Language can break Runtime.TaskSharingContracts, while a change to Runtime.TaskSharingContracts can't break Language.
- Position
- Below the diagonal: Runtime.TaskSharingContracts uses a module listed above it, which is the healthy direction.
39→31 Runtime.TaskSharingContracts uses Language.TaskSharingAnalysis✕
- Connections
- 1 pair of types, where a type in Runtime.TaskSharingContracts uses a type in Language.TaskSharingAnalysis.
- The types involved
FScript.Runtime.TaskSharingContracts.TaskSharingContracts→FScript.Language.TaskSharingAnalysis.Options
- Direction
- Runtime.TaskSharingContracts uses Language.TaskSharingAnalysis, so a change to Language.TaskSharingAnalysis can break Runtime.TaskSharingContracts, while a change to Runtime.TaskSharingContracts can't break Language.TaskSharingAnalysis.
- Position
- Below the diagonal: Runtime.TaskSharingContracts uses a module listed above it, which is the healthy direction.
40→3 JavaScript uses Language✕
- Connections
- 20 pairs of types, where a type in JavaScript uses a type in Language.
- The types involved
FScript.JavaScript.BoundaryHandle→FScript.Language.ExternalCallContextFScript.JavaScript.BoundaryHandle→FScript.Language.TypeFScript.JavaScript.BoundaryHandle→FScript.Language.ValueFScript.JavaScript.JavaScript→FScript.Language.ExtensionRegistrationFScript.JavaScript.JavaScript→FScript.Language.ExternalCallContextFScript.JavaScript.JavaScript→FScript.Language.ExternalFunctionFScript.JavaScript.JavaScript→FScript.Language.HostPermissionsFScript.JavaScript.JavaScript→FScript.Language.MapKeyFScript.JavaScript.JavaScript→FScript.Language.PositionFScript.JavaScript.JavaScript→FScript.Language.SpanFScript.JavaScript.JavaScript→FScript.Language.StmtFScript.JavaScript.JavaScript→FScript.Language.TypeFScript.JavaScript.JavaScript→FScript.Language.ValueFScript.JavaScript.LoadedScriptHandle→FScript.Language.ExtensionRegistrationFScript.JavaScript.LoadedScriptHandle→FScript.Language.TypeFScript.JavaScript.LoadedScriptHandle→FScript.Language.ValueFScript.JavaScript.ParsedProgramHandle→FScript.Language.ExtensionRegistrationFScript.JavaScript.ParsedProgramHandle→FScript.Language.StmtFScript.JavaScript.SessionHandle→FScript.Language.ExtensionRegistrationFScript.JavaScript.TypedProgramHandle→FScript.Language.ExtensionRegistration
- Direction
- JavaScript uses Language, so a change to Language can break JavaScript, while a change to JavaScript can't break Language.
- Position
- Below the diagonal: JavaScript uses a module listed above it, which is the healthy direction.
40→22 JavaScript uses Language.TypeInfer✕
- Connections
- 2 pairs of types, where a type in JavaScript uses a type in Language.TypeInfer.
- The types involved
FScript.JavaScript.JavaScript→FScript.Language.TypeInfer.TypedStmtFScript.JavaScript.TypedProgramHandle→FScript.Language.TypeInfer.TypedStmt
- Direction
- JavaScript uses Language.TypeInfer, so a change to Language.TypeInfer can break JavaScript, while a change to JavaScript can't break Language.TypeInfer.
- Position
- Below the diagonal: JavaScript uses a module listed above it, which is the healthy direction.
40→37 JavaScript uses Language.Interactive✕
- Connections
- 1 pair of types, where a type in JavaScript uses a type in Language.Interactive.
- The types involved
FScript.JavaScript.SessionHandle→FScript.Language.Interactive.Session
- Direction
- JavaScript uses Language.Interactive, so a change to Language.Interactive can break JavaScript, while a change to JavaScript can't break Language.Interactive.
- Position
- Below the diagonal: JavaScript 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 | 55 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 10 | High / Critical |
| A02:2025 — Security Misconfiguration | 2 | High / Critical |
Roadmap
Top priorities: Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce; Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up; Resolve the 3 EmptyCatchBlock finding(s) in Explicit Debt — start with NativeGraphics.cs, DebuggerEntry.cs, LspHandlers.cs.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 3 EmptyCatchBlock finding(s) in Explicit Debt — start with NativeGraphics.cs, DebuggerEntry.cs, LspHandlers.cs. | +3.8 pts | Low | Explicit Debt |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +3.9 pts | Medium | Observability |
| Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up. | +3.8 pts | Medium | Type Safety |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with FScript.LanguageServer.csproj. | +1.6 pts | Low | ADR Quality |
| Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package. | +2.8 pts | Medium | Large Files |
| TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants. | +2.4 pts | Medium | Async & latency hygiene |
| Resolve the 13 FileTooLong finding(s) in God Classes — start with LspSymbols.fs, TypeInfer.fs, LspHandlers.fs. | +2.6 pts | High | God Classes |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +1.2 pts | Medium | Architecture documentation |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.1 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| src/FScript.LanguageServer/LspHandlers.cs | 5.4 | Mixed | Explicit Debt: EmptyCatchBlock |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs | 7.0 | Near-clean | God Classes: FileTooLong: LanguageServer/LspSymbols.fs |
| src/FScript.Language/TypeInfer.fs | 7.0 | Near-clean | God Classes: FileTooLong: FScript.Language/TypeInfer.fs |
| src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs | 7.0 | Near-clean | God Classes: FileTooLong: LanguageServer/LspHandlers.fs |
| src/FScript.Language/Parser.fs | 7.0 | Near-clean | God Classes: FileTooLong: FScript.Language/Parser.fs |
| src/FScript.Compiler/Lir.fs | 7.0 | Near-clean | God Classes: FileTooLong: FScript.Compiler/Lir.fs |
| src/FScript.Language/IncludeResolver.fs | 7.0 | Near-clean | God Classes: FileTooLong: FScript.Language/IncludeResolver.fs |
| src/FScript.Language/BuiltinFunctions.fs | 7.1 | Near-clean | God Classes: FileTooLong: FScript.Language/BuiltinFunctions.fs |
| src/FScript.Language/Eval.fs | 7.2 | Near-clean | God Classes: FileTooLong: FScript.Language/Eval.fs |
| src/FScript.JavaScript/Library.fs | 7.2 | Near-clean | God Classes: FileTooLong: FScript.JavaScript/Library.fs |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 51 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 51 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, 226 of 238 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D1 Cyclomatic Complexity — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the .NET half could not be measured — no coverage produced (collector absent, or test run exceeded the inline budget); the JavaScript/TypeScript half measured 100.0% (node:test in src/FScript.JavaScript/: not run; node:test via `npm ci --ignore-scripts` in vscode-fscript/). This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
- D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 63 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 76 test source file(s) (.fs, .js, .mjs) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: /usr/share/dotnet/sdk/10.0.400/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.TargetFrameworkInference.targets(184,5): error NETSDK1045: The current .NET SDK does not support targeting .NET 11.0. Either target .NET 10.0 or lower, or use a version of the .NET SDK that supports .NET 11.0. Download the ….
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D15 Churn × Complexity Hotspots — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. A hotspot is churn × complexity. Churn was measured (94960 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-contributor repository — bus factor is not applicable (1 contributor(s) across 421 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'src/FScript.Language/FScript.Language.fsproj' because the file extension '.fsproj' is not associated with a language.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 3 deducted marker(s) and the 0.9/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (27,084 lines, 91% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D23 Boundary Type-Coupling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (29,862 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can 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 — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — 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 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. 2 of 3 declared ecosystem(s) (npm,osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `.github/scripts/fscript-formula-template.rb`, `src/FScript.Backend.CSharp/RuntimeSDK.cs`, `src/FScript.DebugAdapter/Protocol.cs`, `website/docusaurus.config.ts` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X28 Index access outside its own emptiness guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for src/FScript.Compiler/FScript.Compiler.fsproj, src/FScript/FScript.fsproj, tests/FScript.Language.Tests/FScript.Language.Tests.fsproj, tests/FScript.Compiler.Tests/FScript.Compiler.Tests.fsproj, tests/FScript.Runtime.Tests/FScript.Runtime.Tests.fsproj and 19 more, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- 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.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- 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 checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D3 · God Classes
16 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 13 FileTooLong finding(s) in God Classes — start with LspSymbols.fs, TypeInfer.fs, LspHandlers.fs. — One of this dimension's main actionable groups (13 warning-level).
- Resolve the 3 FunctionTooLong finding(s) in God Classes — start with sandbox.tsx, index.tsx, extension.js. — One of this dimension's main actionable groups (3 warning-level).
D4 · Code Duplication
110 duplicated block group(s) detected. 7.5 % of the production lines (2,240 of 29,862) are in a reported copy. One further row reports members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 13 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with Lir.fs (3), TypeInfer.fs (2), DotNetCollectionRepresentations.fs. — One of this dimension's main actionable groups (13 warning-level).
- Resolve the 10 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with TypeInfer.fs (4), Lir.fs (2), DotNetCollectionFusion.fs. — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 10 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with LspHandlers.fs (3), TypeInfer.fs (2), LirCommonSubexpressions.fs. — One of this dimension's main actionable groups (10 warning-level).
D5 · Coupling
4 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
1 of 6 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with IGraphics.cs. — One of this dimension's main actionable groups (1 warning-level).
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 63 tests. Measured on the C# suite only — at least 76 test source file(s) (.fs, .js, .mjs) went unread, so its test quality is unmeasured and is not in these counts.
D11 · Test Reliability
0 flaky across 2 measured tier(s). unit: measured (0 flaky); JavaScript/TypeScript (node:test via `npm install --ignore-scripts` (no lockfile) in src/FScript.JavaScript/ (3 tests); node:test via `npm ci --ignore-scripts` in vscode-fscript/ (47 tests)): measured (0 flaky).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 182 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 17 direct `PackageReference`(s), and 127 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. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D17 · Explicit Debt
3 deducted debt markers + unmeasured dead symbols across 1188 LoC in the .NET projects (0.9/KLoC) → score 8.1. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (91% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
What to do
- Resolve the 3 EmptyCatchBlock finding(s) in Explicit Debt — start with NativeGraphics.cs, DebuggerEntry.cs, LspHandlers.cs. — One of this dimension's main actionable groups (3 issue-level).
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 100 document(s) read across 6 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with FScript.LanguageServer.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 4 projects flagged as possibly oversized/incoherent.
D27 · Navigability
77 % of calls cross a namespace and 2 % go through an interface, but 79 % of collaborators are co-located — so following a call takes several hops. 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)
55 finding(s): 0 critical, 55 high, 0 medium, 0 low. 42 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. semgrep hit a parse error in 4 file(s) — `.github/scripts/fscript-formula-template.rb` (line 2), `src/FScript.Backend.CSharp/RuntimeSDK.cs` (lines 15–21, line 127), `src/FScript.DebugAdapter/Protocol.cs` (line 9), `website/docusaurus.config.ts` (line 52, line 113) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 2 of those file(s) — `src/FScript.Backend.CSharp/RuntimeSDK.cs`, `src/FScript.DebugAdapter/Protocol.cs` — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. Separately, one or more rules could not re-parse an embedded snippet in 3 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 5 REDACTED finding(s) charged to Static Analysis (SAST) — the other 42 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (47 issue-level, 5 of them charged here).
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D30 · Dependency Vulnerabilities
3 finding(s): 0 critical, 1 high, 2 medium, 0 low. Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,osv), and the findings above are real and complete for them. nuget was not scanned (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), so this is not the whole dependency surface and the result is reported at reduced confidence.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D31 · IaC & Container Security
2 finding(s): 0 critical, 1 high, 1 medium, 0 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 82 of the 107 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: Ast.fs↔Lexer.fs 55%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with Ast.fs. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
2/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 — start with REDACTED. — 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).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 25 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX8 · Test isolation
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
- vscode-fscript/README.md names Node.js 22, but the repository declares engines `>=20.0`. 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. — vscode-fscript/README.md:3
- website/README.md names TypeScript 7, but the manifest declares `typescript` ~5.9.3. 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. — website/README.md:5
- docs/guides/compile-to-dotnet.md names .NET 10, but the projects target .NET 11. 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/guides/compile-to-dotnet.md:202
- website/docs/compiler/compile-to-dotnet.md names .NET 10, but the projects target .NET 11. 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. — website/docs/compiler/compile-to-dotnet.md:259
What to do
- Reconcile the README with reality: vscode-fscript/README.md names Node.js 22, but the repository declares engines `>=20.0`; website/README.md names TypeScript 7, but the manifest declares `typescript` ~5.9.3; docs/guides/compile-to-dotnet.md names .NET 10, but the projects target .NET 11; website/docs/compiler/compile-to-dotnet.md names .NET 10, but the projects target .NET 11.
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 7 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
- `samples/ffi/Provider/FfiSample.fsproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — samples/ffi/Provider/FfiSample.fsproj:11
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF3 · Async & latency hygiene
- `fs.existsSync` in `createServerOptions` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×3) — vscode-fscript/extension.js:89, vscode-fscript/extension.js:103, vscode-fscript/extension.js:146
- `fs.writeFileSync` in `openJsonInTempFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — vscode-fscript/extension.js:393
- 11 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
- `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×10) — src/FScript.DebugAdapter/DebuggerEntry.cs:41, src/FScript.DebugAdapter/DebuggerEntry.cs:168, src/FScript.DebugAdapter/DebuggerEntry.cs:169, …
- `configured.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). — src/FScript.DebugAdapter/DebuggerEntry.cs:275
What to do
- TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
- Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
R1 · Type Safety
- 0 typed · 19 plain JS — the untyped files are src/FScript.JavaScript/scripts/prepare-package.mjs, src/FScript.JavaScript/test/fable.test.mjs, src/FScript.JavaScript/test/hosting.test.mjs, src/FScript.JavaScript/test/support-library.test.mjs, tests/FScript.DebugAdapter.Tests/AdapterTests.js, tests/FScript.DebugAdapter.Tests/EventWait.js (+13 more).
What to do
- Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication
- vscode-fscript/extension.js:442 · vscode-fscript/extension.js:458 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — vscode-fscript/extension.js:442
- vscode-fscript/extension.js:846 · vscode-fscript/extension.js:936 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — vscode-fscript/extension.js:846
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
- startFolderClient has cyclomatic complexity 17 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-fscript/extension.js:548
- resolveDebugConfigurationWithSubstitutedVariables has cyclomatic complexity 17 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-fscript/extension.js:866
- updateConfigurationStatus has cyclomatic complexity 17 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-fscript/extension.js:732
- (anonymous) has cyclomatic complexity 14 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-fscript/extension.js:1033
- deactivate has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-fscript/extension.js:1060
- createServerOptions has cyclomatic complexity 11 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-fscript/extension.js:81
- require has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — tests/FScript.LanguageServer.Tests/ExtensionStartupTests.js:120
R3 · Large Files
- vscode-fscript/extension.js has 1003 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — vscode-fscript/extension.js:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. — src/FScript.JavaScript/scripts/prepare-package.mjs:1
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
R6 · Tooling
R7 · Dead Code
- 10 file(s) (~1076 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package.
R8 · Dependency Hygiene
R9 · Circular Imports
X20 · Mistyped argument guard
X5 · Nullable reference types
- ~0.9 `!` suppressions per 1k syntax nodes — 9 suppression(s) across the 10066 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 49% | Adequate — gated by R1, R3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 98% | Exemplary | Strongest area. |
| Maturity | 66% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 48% | Adequate — gated by P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 71% | Adequate — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 60% | Adequate | Acceptable, with room to improve. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 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 — 76 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — no DI registrations detected
- AX2 Stateful singletons — no singleton implementations detected
- AX6 Interface segregation — AX6 reached only 13% of this repository's production lines — fsharp (27,084 lines), vba (17 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — 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 — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- 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
- 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-contributor 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 .bas, .fs, .ts, .tsx, 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 — D21 withholds its case and prefix conventions rows: 1 candidate(s) found and not reported.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed F# surface was not measured.
- D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .fs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 4 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — .NET suite
- DM1 Domain Modelling — applicable but not scored (3 signals for this style, 3 needed — the count is met but a required primary signal is absent): 3 strongly-typed id(s); 166 value object(s); 3 domain event(s); its domain events are published by services or handlers — no domain entity raises one; no aggregate is declared and no domain structure surrounds the state-guarding types: not claimed as DDD
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — IC1 reached only 7% of this repository's production lines — fsharp (27,084 lines), javascript (1,228 lines), typescript (743 lines), vba (17 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- P12 CI test-gate honesty — 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.
- 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 — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- 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.
- X1 Async correctness — X1 reached only 7% of this repository's production lines — fsharp (27,084 lines), javascript (1,228 lines), typescript (743 lines), vba (17 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — X12 reached only 7% of this repository's production lines — fsharp (27,084 lines), javascript (1,228 lines), typescript (743 lines), vba (17 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — X16 reached only 7% of this repository's production lines — fsharp (27,084 lines), javascript (1,228 lines), typescript (743 lines), vba (17 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — X18 reached only 7% of this repository's production lines — fsharp (27,084 lines), javascript (1,228 lines), typescript (743 lines), vba (17 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — X2 reached only 7% of this repository's production lines — fsharp (27,084 lines), javascript (1,228 lines), typescript (743 lines), vba (17 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — X22 reached only 7% of this repository's production lines — fsharp (27,084 lines), javascript (1,228 lines), typescript (743 lines), vba (17 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — X27 reached only 7% of this repository's production lines — fsharp (27,084 lines), javascript (1,228 lines), typescript (743 lines), vba (17 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X28 Index access outside its own emptiness guard — X28 reached only 7% of this repository's production lines — fsharp (27,084 lines), javascript (1,228 lines), typescript (743 lines), vba (17 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — X3 reached only 7% of this repository's production lines — fsharp (27,084 lines), javascript (1,228 lines), typescript (743 lines), vba (17 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 60 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- EmptyCatchBlock samples/ffi/Renderer/NativeGraphics.cs:59
- EmptyCatchBlock src/FScript.DebugAdapter/DebuggerEntry.cs:288
- EmptyCatchBlock src/FScript.LanguageServer/LspHandlers.cs:208
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 165 finding(s)
- Sync-over-async blocking vscode-fscript/extension.js:89
- Sync-over-async blocking vscode-fscript/extension.js:103
- Sync-over-async blocking vscode-fscript/extension.js:146
- Sync-over-async blocking vscode-fscript/extension.js:393
- Sync-over-async blocking
- Sync-over-async blocking src/FScript.DebugAdapter/DebuggerEntry.cs:41
- Sync-over-async blocking src/FScript.DebugAdapter/DebuggerEntry.cs:168
- Sync-over-async blocking src/FScript.DebugAdapter/DebuggerEntry.cs:169
- Sync-over-async blocking src/FScript.DebugAdapter/DebuggerEntry.cs:180
- Sync-over-async blocking src/FScript.DebugAdapter/DebuggerEntry.cs:181
- Sync-over-async blocking src/FScript.DebugAdapter/DebuggerEntry.cs:205
- Sync-over-async blocking src/FScript.DebugAdapter/DebuggerEntry.cs:206
- Sync-over-async blocking src/FScript.DebugAdapter/DebuggerEntry.cs:284
- Sync-over-async blocking src/FScript.DebugAdapter/DebuggerEntry.cs:285
- Sync-over-async blocking src/FScript.DebugAdapter/DebuggerEntry.cs:286
- Sync-over-async blocking src/FScript.DebugAdapter/DebuggerEntry.cs:275
- FileTooLong: LanguageServer/LspSymbols.fs src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs
- FileTooLong: FScript.Language/TypeInfer.fs src/FScript.Language/TypeInfer.fs
- FileTooLong: LanguageServer/LspHandlers.fs src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs
- FileTooLong: FScript.Language/Parser.fs src/FScript.Language/Parser.fs
- FileTooLong: FScript.Backend.CSharp/CSharpBackend.fs src/FScript.Backend.CSharp/CSharpBackend.fs
- FileTooLong: FScript.Language/Eval.fs src/FScript.Language/Eval.fs
- FileTooLong: FScript.Compiler/Lir.fs src/FScript.Compiler/Lir.fs
- FileTooLong: FScript.JavaScript/Library.fs src/FScript.JavaScript/Library.fs
- FileTooLong: vscode-fscript/extension.js vscode-fscript/extension.js
- FileTooLong: FScript.Interpreter.Lir/LirInterpreter.fs src/FScript.Interpreter.Lir/LirInterpreter.fs
- FileTooLong: FScript.Language/IncludeResolver.fs src/FScript.Language/IncludeResolver.fs
- FileTooLong: FScript.Language/BuiltinFunctions.fs src/FScript.Language/BuiltinFunctions.fs
- FileTooLong: FScript.Compiler/IrArtifact.fs src/FScript.Compiler/IrArtifact.fs
- Duplicated block (5 lines × 2) src/FScript.Backend.DotNet/DotNetCollectionRepresentations.fs:105
- Duplicated block (5 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspModel.fs:164
- Duplicated block (5 lines × 2) src/FScript.Compiler/IrArtifact.fs:70
- Duplicated block (5 lines × 2) src/FScript.Compiler/Lir.fs:795
- Duplicated block (5 lines × 2) src/FScript.Language/Pretty.fs:8
- Duplicated block (5 lines × 2) src/FScript.Language/TypeInfer.fs:928
- Duplicated block (5 lines × 2) src/FScript.Runtime/RegexExterns.fs:8
- Duplicated block (5 lines × 2) src/FScript.Backend.DotNet/DotNetOptimization.fs:13
- Duplicated block (5 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs:2368
- Duplicated block (5 lines × 2) src/FScript.Compiler/Lir.fs:337
- Duplicated block (5 lines × 2) src/FScript.Compiler/Lir.fs:960
- Duplicated block (5 lines × 2) src/FScript.Language/TypeInfer.fs:2326
- Duplicated block (5 lines × 2) src/FScript.Runtime/Decode.fs:191
- Duplicated block (7 lines × 2) src/FScript.Backend.DotNet/DotNetCollectionFusion.fs:45
- Duplicated block (7 lines × 2) src/FScript.Compiler/Lir.fs:327
- Duplicated block (7 lines × 2) src/FScript.Compiler/Lir.fs:938
- Duplicated block (7 lines × 2) src/FScript.Language/BuiltinFunctions.fs:640
- Duplicated block (7 lines × 2) src/FScript.Language/TypeInfer.fs:1583
- Duplicated block (7 lines × 2) src/FScript.Language/TypeInfer.fs:1370
- Duplicated block (7 lines × 2) src/FScript.Language/Parser.fs:245
- Duplicated block (7 lines × 2) src/FScript.Runtime/FsExterns.fs:67
- Duplicated block (7 lines × 2) src/FScript.Language/TypeInfer.fs:28
- Duplicated block (7 lines × 2) src/FScript.Language/TypeInfer.fs:1758
- Duplicated block (6 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs:1471
- Duplicated block (6 lines × 2) src/FScript.Compiler/LirCommonSubexpressions.fs:59
- Duplicated block (6 lines × 2) src/FScript.JavaScript/Library.fs:607
- Duplicated block (6 lines × 2) src/FScript.Language/Lexer.fs:67
- Duplicated block (6 lines × 2) src/FScript.Language/TypeInfer.fs:163
- Duplicated block (6 lines × 2) src/FScript.Runtime/Decode.fs:41
- Duplicated block (6 lines × 2) src/FScript.Backend.DotNet/DotNetCollectionFusion.fs:32
- Duplicated block (6 lines × 2) src/FScript.Language/TypeInfer.fs:1147
- Duplicated block (6 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs:803
- Duplicated block (6 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs:664
- Duplicated block (8 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs:656
- Duplicated block (8 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs:1002
- Duplicated block (8 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs:1576
- Duplicated block (8 lines × 2) src/FScript.Language/BuiltinFunctions.fs:438
- Duplicated block (8 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs:341
- Duplicated block (8 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs:1316
- Duplicated block (8 lines × 2) src/FScript.Language/Parser.fs:664
- Duplicated block (8 lines × 2) src/FScript.Compiler/HirLowering.fs:35
- Duplicated block (11 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs:902
- Duplicated block (11 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs:1048
- Duplicated block (11 lines × 2) src/FScript.Compiler/Hir.fs:47
- Duplicated block (11 lines × 2) src/FScript.Language/Parser.fs:845
- Duplicated block (11 lines × 2) src/FScript.Language/Parser.fs:878
- Duplicated block (11 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs:1173
- Duplicated block (12 lines × 2) src/FScript.Compiler/Hir.fs:16
- Duplicated block (12 lines × 2) src/FScript.Compiler/HirLowering.fs:128
- Duplicated block (12 lines × 2) src/FScript.Language/IncludeResolver.fs:277
- Duplicated block (12 lines × 2) src/FScript.Backend.CSharp/CSharpBackend.fs:586
- Duplicated block (7–8 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs:885
- Duplicated block (7–8 lines × 2) src/FScript.Compiler/Lir.fs:547
- Duplicated block (7–8 lines × 2) src/FScript.Compiler/Lir.fs:556
- Duplicated block (7–8 lines × 2) src/FScript.Language/TypeInfer.fs:1060
- FunctionTooLong: sandbox.Sandbox website/src/pages/sandbox.tsx:105
- FunctionTooLong: index.Home website/src/pages/index.tsx:189
- FunctionTooLong: extension.activate vscode-fscript/extension.js:910
- Duplicated block (17 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs:854
- Duplicated block (17 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs:821
- Duplicated block (17 lines × 2) src/FScript.Language/TypeInfer.fs:1034
- Duplicated block (14 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspModel.fs:171
- Duplicated block (14 lines × 2) src/FScript.Language/Eval.fs:115
- Duplicated block (14 lines × 2) src/FScript.Language/Eval.fs:130
- Duplicated block (13 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs:1489
- Duplicated block (13 lines × 2) src/FScript.Language/TypeInfer.fs:1200
- Duplicated block (13 lines × 2) src/FScript.Language/IncludeResolver.fs:156
- Duplicated block (9–10 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs:167
- Duplicated block (9–10 lines × 2) src/FScript.JavaScript/Library.fs:637
- Duplicated block (9–10 lines × 2) src/FScript.Language/Parser.fs:828
- Duplicated block (8 lines × 3) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs:914
- Duplicated block (8 lines × 3) src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs:830
- Duplicated block (8 lines × 3) src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs:2015
- Duplicated block (7 lines × 3) src/FScript.Interpreter.Lir/LirInterpreter.fs:60
- Duplicated block (7 lines × 3) src/FScript.Language/Parser.fs:837
- Duplicated block (7 lines × 3) src/FScript.Language/BuiltinFunctions.fs:638
- REDACTED
- REDACTED
- Duplicated block (22 lines × 2) src/FScript.LanguageServer/LspHandlers.cs:39
- Duplicated block (22 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs:598
- Duplicated block (21 lines × 2) src/FScript.Compiler/Hir.fs:59
- Duplicated block (21 lines × 2) src/FScript.Language/Parser.fs:1313
- Duplicated block (16 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs:1626
- Duplicated block (16 lines × 2) src/FScript.Language/TypeInfer.fs:973
- Duplicated block (10 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs:1082
- Duplicated block (10 lines × 2) src/FScript.Language/IncludeResolver.fs:175
- Duplicated block (9 lines × 4) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs:428
- Duplicated block (9 lines × 4) src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs:1271
- Duplicated block (8–9 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs:1733
- Duplicated block (8–9 lines × 2) src/FScript.Language/Eval.fs:1222
- Duplicated block (9 lines × 2) src/FScript.Language/TypeInfer.fs:972
- Duplicated block (9 lines × 2) src/FScript.Language/TypeInfer.fs:1378
- Duplicated block (6 lines × 3) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs:307
- Duplicated block (6 lines × 3) src/FScript.Language/BuiltinFunctions.fs:655
- REDACTED
- Change coupling: Ast.fs ↔ Lexer.fs src/FScript.Language/Ast.fs:1
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (39 corresponding lines) src/FScript.LanguageServer/LspHandlers.cs:38
- Duplicated block (45 lines × 2) src/FScript.Language/Parser.fs:1334
- Duplicated block (27–29 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs:336
- Duplicated block (28 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs:824
- Duplicated block (27–28 lines × 2) src/FScript.Language/BuiltinFunctions.fs:111
- Duplicated block (25 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs:1866
- Duplicated block (21–22 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs:1152
- Duplicated block (18 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs:1402
- Duplicated block (17–18 lines × 2) src/FScript.Language/IncludeResolver.fs:649
- Duplicated block (15–17 lines × 2) src/FScript.Language/IncludeResolver.fs:667
- Duplicated block (15–16 lines × 3) src/FScript.Language/IncludeResolver.fs:619
- Duplicated block (15–16 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs:556
- Duplicated block (11–16 lines × 2) src/FScript.JavaScript/Library.fs:624
- Duplicated block (14–15 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs:1193
- Duplicated block (12–14 lines × 2) src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs:1473
- Duplicated block (13–14 lines × 2) src/FScript.Interpreter.Lir/LirInterpreter.fs:510
- Duplicated block (13 lines × 3) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs:425
- Duplicated block (10–11 lines × 2) src/FScript.Language/Parser.fs:1379
- Duplicated block (9 lines × 3) src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs:2779
- Duplicated block (6 lines × 5) src/FScript.CSharpInterop/LanguageServer/LspHandlers.fs:411
- Duplicated block (7 lines × 4) src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs:2777
- Duplicated block (5 lines × 3) src/FScript.CSharpInterop/LanguageServer/LspSymbols.fs:2005
- Low cohesion: RecordingGraphics (LCOM4 4) samples/ffi/Renderer/IGraphics.cs:16
- No structured logging
- Type Safety
- Duplicated block (14 lines × 2 locations) vscode-fscript/extension.js:442
- Duplicated block (11 lines × 2 locations) vscode-fscript/extension.js:846
- Complex function startFolderClient (cyclomatic 17, cognitive 20) vscode-fscript/extension.js:548
- Complex function resolveDebugConfigurationWithSubstitutedVariables (cyclomatic 17, cognitive 19) vscode-fscript/extension.js:866
- Complex function updateConfigurationStatus (cyclomatic 17, cognitive 15) vscode-fscript/extension.js:732
- Complex function (anonymous) (cyclomatic 14, cognitive 22) vscode-fscript/extension.js:1033
- Complex function deactivate (cyclomatic 13, cognitive 12) vscode-fscript/extension.js:1060
- Complex function createServerOptions (cyclomatic 11, cognitive 12) vscode-fscript/extension.js:81
- Complex function require (cyclomatic 11, cognitive 10) tests/FScript.LanguageServer.Tests/ExtensionStartupTests.js:120
- vscode-fscript/extension.js: 1003 lines of code vscode-fscript/extension.js:1
- No test reaches this file src/FScript.JavaScript/scripts/prepare-package.mjs:1
- NuGet dependencies are not locked
Minor — 13 finding(s)
- README/code drift vscode-fscript/README.md:3
- README/code drift website/README.md:5
- README/code drift docs/guides/compile-to-dotnet.md:202
- README/code drift website/docs/compiler/compile-to-dotnet.md:259
- No ADRs found src/FScript.LanguageServer/FScript.LanguageServer.csproj:3
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No SAST REDACTED:4
- No dependency-update automation samples/ffi/Provider/FfiSample.fsproj:11
- Null-forgiving operator (`!`) suppressions override nullable warnings
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d8629a17bad742e0bb6e2af3ab9f8d02/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d8629a17bad742e0bb6e2af3ab9f8d02/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 55 | 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 | — |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 3 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 2 | artifacts/raw/trivy-config.json |
| 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. semgrep could not parse 4 file(s) — `.github/scripts/fscript-formula-template.rb`, `src/FScript.Backend.CSharp/RuntimeSDK.cs`, `src/FScript.DebugAdapter/Protocol.cs`, `website/docusaurus.config.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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 | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |