Public report of JetBrains/resharper-fsharp, published 13 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.3). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 13 November 2026, 11:41 UTC · Survey ID cd_9905488361154c9a89fb0e4e9a59fdad

JetBrains/resharper-fsharp

Measured 13 November 2026, 11:40 UTC, at code version 5a9f28b

Code coverage is not measured: No coverage collector is wired up.

Boundary Type-Coupling is not measured: Bounded contexts not declared.

Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.

CAI score 42out of 100 Weak
CriticalWeakAdequateStrongExemplary
Down 8 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A medium codebase: 71,226 lines of product code in 10 projects, tests not counted · Estimated rebuild effort: about 1.1 person-years · Weakest lens: Code Health, 29

Findings by how serious they are

31 critical 125 serious 25 minor

16 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
13 November 2026, 11:40 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

31of 31 dimensions measured by tools.
170of 181 findings point to an exact file and line, so you can open each one in the code. The other 11 concern the repository as a whole, such as missing documentation.
31dimensions across 6 lenses, read from 71,226 lines of product code in 10 projects.
Chapters

Executive summary

JetBrains/resharper-fsharp falls short of our standard for production, in part because it has sets of compiler warnings switched off in projects. It scores 42 out of 100 and is rated Weak, and 20 of its 31 critical findings are security problems.

Code Health, at 29, is the weakest lens and counts most in the score. The best first step is fixing the silenced warnings, worth about 12 points. Replacing the six exposed passwords or keys and switching the old ones off comes next, worth about 4 points. Raising Code Health to 70 would lift the score to about 52.

Six passwords or keys in the code and six in the code's history are open to anyone who can read the repository. Six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and two weaknesses in the code could be used by an attacker. Replacing each exposed password or key, pinning each tool to an exact version and fixing the weaknesses the scanner points to would close these risks. The 11 sets of compiler warnings switched off in projects need turning back on in the build file.

The product code is 71,226 lines, about €160,000 to rebuild. The check for malicious packages couldn't finish, so that result is missing, not a clean pass.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Code Health 29 · counts for 46%Security and Compliance 42 · counts for 25%Production Readiness 48 · counts for 14%Maturity 58 · counts for 8%Architecture 100 · counts for 4%Performance 100 · counts for 2%

If Code Health rose from 29 to 70, the lowest score rated Strong, the score would rise from 42 to about 52.

Code composition: what the lines of code are
Business logic 12%Supporting code 24%Tests 65%
New since the last survey: 25 findings

These 25 critical or serious findings weren't in the previous survey, on 24 October 2026.

  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateLambdaRule.fs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/NameSuggestionRule.fs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ImportMemberFix.fs
  • Code Duplication · Edited copies of one member (3 members, 19+ corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveRedundantAttributeParensFix.fs
  • Code Duplication · Edited copy of a member (20 corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveUnnecessaryUpcastFix.fs
  • Code Duplication · Edited copy of a member (15 corresponding lines) rider-fsharp/src/main/java/com/jetbrains/rider/plugins/fsharp/projectView/FSharpMoveProviderExtension.kt
  • Code Duplication · Edited copy of a member (17 corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveConstructorFix.fs
  • Code Duplication · Edited copy of a member (9 corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Comment/FSharpDocCommentElementsItemsProvider.fs
  • Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Common/src/ProjectModel/Host/ZoneMarker.fs
  • Code Duplication · Edited copy of a member (8 corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/AI/ZoneMarker.fs
  • Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Common/src/Checker/ZoneMarker.fs
  • Code Duplication · Edited copies of one member (4 members, 8+ corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/PsiFeaturesNamespaceZoneMarker.fs
  • Code Duplication · Duplicated block (20–22 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/StringLiteralsUtil.fs
  • Code Duplication · Duplicated block (9 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateMatchExprPatternsRule.fs
  • Code Duplication · Duplicated block (5 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateMatchExprPatternsRule.fs
  • Change Coupling · Change coupling: FsiHost.fs ↔ SandboxDocumentLanguageSupportFSharpScript.fs ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Fsi/FsiHost.fs
  • Platform End-of-Life · End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/ConsoleAppTwoTargetFrameworks/CoreConsoleApp.fsproj
  • Platform End-of-Life · End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/CoreConsoleApp/CoreConsoleApp.fsproj
  • Platform End-of-Life · End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/CsvTypeProvider/TypeProviderLibrary/TypeProviderLibrary.fsproj
  • Platform End-of-Life · End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/FableApp/FableApp.fsproj
  • Platform End-of-Life · End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/ReferencesOrder/ReferencesOrder.fsproj
  • Platform End-of-Life · End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/SwaggerProviderCSharp/CSharpLibrary/CSharpLibrary.csproj
  • Platform End-of-Life · End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/SwaggerProviderCSharp/SwaggerProviderLibrary/SwaggerProviderLibrary.fsproj
  • Platform End-of-Life · End-of-life runtime: .NET netcoreapp3.1 ReSharper.FSharp/src/FSharp.TypeProviders.Host/FSharp.TypeProviders.Host.NetCore/FSharp.TypeProviders.Host.NetCore.csproj
  • Platform End-of-Life · End-of-life runtime: .NET netcoreapp3.1 rider-fsharp/src/test/testData/solutions/FormatCodeApp/FormatCodeApp/FormatCodeApp.fsproj

We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 16 findings

These 16 critical or serious findings were in the previous survey, on 24 October 2026, and are gone from this one.

  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateLambdaRule.fs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/NameSuggestionRule.fs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ImportMemberFix.fs
  • Code Duplication · Duplicated block (6 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/UnionCasePatternRule.fs
  • Code Duplication · Duplicated block (6 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/FSharpBindUtil.fs
  • Code Duplication · Duplicated block (27 lines × 2) rider-fsharp/projectTemplates/FSharpClassLibraryTemplate/AssemblyInfo.fs
  • Code Coverage · Coverage not measured — no coverage collector is wired up
  • Test Distribution · Tests outside the analyzed solution
  • Change Coupling · Change coupling clique: FSharpVcsCodeVisionRangesProviderStage.fs, FsiHost.fs, SandboxDocumentLanguageSupportFSharpScript.fs ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Stages/FSharpVcsCodeVisionRangesProviderStage.fs
  • Change Coupling · Change coupling: FsiOptionsPage.fs ↔ FSharpQuickDefinitionService.fs ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Fsi/FsiOptionsPage.fs
  • Change Coupling · Change coupling: FSharpGeneratedMemberBase.cs ↔ FSharpTypeMember.cs ReSharper.FSharp/src/FSharp/FSharp.Psi/src/Impl/DeclaredElement/CompilerGenerated/FSharpGeneratedMemberBase.cs
  • Change Coupling · Change coupling: REDACTED ↔ REDACTED REDACTED
  • Change Coupling · Change coupling: FSharpCodeStructure.fs ↔ FSharpQuickDefinitionService.fs ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeStructure/FSharpCodeStructure.fs
  • Platform End-of-Life · End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/SwaggerProviderCSharp/CSharpLibrary/CSharpLibrary.csproj
  • Platform End-of-Life · End-of-life runtime: .NET netcoreapp3.1 ReSharper.FSharp/src/FSharp.TypeProviders.Host/FSharp.TypeProviders.Host.NetCore/FSharp.TypeProviders.Host.NetCore.csproj
  • Documentation (README) · README may be stale
Rebuild cost: about €160,000 · Estimate
Cost to rebuild€54,000 to €270,000, for 896 to 2,864 hours of work, about 1.1 person-years for 1 to 3 engineers
Difficulty of the problemStandard, 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 42. 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.
SizeMedium: 71,226 lines of product code
Comment linesThe estimate prices 70,731 lines. Comment lines count towards the size of 71,226 lines but aren't priced as work.
What it is notNot 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.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 11 NoWarnInCsproj finding(s) in Explicit Debt — start with FSharp.Fantomas.Host.csproj (2), FSharp.TypeProviders.Host.NetCore.csproj (2), FSharp.Debugger.csproj.
Raises the score by about 12 points · Medium effort · Explicit Debt
2
Resolve the 6 Leaked secret finding(s) in Secret Scanning — start with REDACTED (5), REDACTED.
Raises the score by about 4 points · Low effort · Secret Scanning
3
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Raises the score by about 9 points · Medium effort · Nullable reference types

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €160,000 to build again, about 1.1 person-years of work. Its weakest lens is Code Health, at 29 (Weak). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Resolve the 11 NoWarnInCsproj finding(s) in Explicit Debt. Of all the actions in this report, it raises the score most for the work it takes: about 12 points for medium effort, because it clears the 11 Explicit Debt findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — bounded-context dependency graph

Each box is a bounded context (its layer projects grouped, or a project count when large); arrows show dependencies between contexts. A shared kernel is where many arrows converge.

arch Debugger Debugger Fantomas.Host Fantomas.Host Fantomas.Protocol Fantomas.Protocol ProjectModelBase ProjectModelBase Psi Psi ctx:FSharp FSharp Common · Daemon · Features · Intentions … Psi->ctx:FSharp TypeProviders.Host TypeProviders.Host TypeProviders.Host.NetCore TypeProviders.Host.NetCore TypeProviders.Protocol TypeProviders.Protocol ctx:RiderPlugin (ReSharper.FSharp/src/FSharp.RiderPlugin/proj/src) RiderPlugin (ReSharper.FSharp/src/FSharp.RiderPlugin/proj/src) RiderPlugin/proj/src) ctx:RiderPlugin (ReSharper.FSharp/src/FSharp.RiderPlugin/proj/src)->ctx:FSharp __more__ +2 more contexts

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

273 modules, with 242 dependencies between them. 2 loops run through 8 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 233 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 DocumentRangeExtensions2 FSharpFileSystemPathExtensions3 JetBrains.ReSharper.Plugins.FSharp.Checker.FcsCheckerService4 JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers.Util5 JetBrains.ReSharper.Plugins.FSharp.Psi.Features6 JetBrains.ReSharper.Plugins.FSharp.Util.SettingsStoreUtil7 com.jetbrains.rider.ideaInterop.fileTypes.fsharp.lexer8 JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util9 JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil10 JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil11 com.jetbrains.rider.ideaInterop.fileTypes.fsharp.highlighting12 com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi13 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion14 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext15 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Daemon.Highlightings16 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil17 JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing18 JetBrains.ReSharper.Plugins.FSharp.Psi.Util.OpensUtil19 com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl20 com.jetbrains.rider.plugins.fsharp.services.fsi21 JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages22 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.OverrideMemberRule23 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FSharpNamingService24 JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil25 JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil26 JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer27 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Generate.GenerateOverrides28 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions29 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo30 JetBrains.ReSharper.Plugins.FSharp.Settings31 JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem32 JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts33 JetBrains.ReSharper.Plugins.FSharp.Services.Formatter34 JetBrains.ReSharper.Plugins.FSharp.ProjectModel35 JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders36 JetBrains.ReSharper.Plugins.FSharp.Checker37 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules38 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi39 JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers40 JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader
1 DocumentRangeExtensions
2 FSharpFileSystemPathExtensions
3 JetBrains.ReSharper.Plugins.FSharp.Checker.FcsCheckerService
4 JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers.Util
5 JetBrains.ReSharper.Plugins.FSharp.Psi.Features
6 JetBrains.ReSharper.Plugins.FSharp.Util.SettingsStoreUtil
7 com.jetbrains.rider.ideaInterop.fileTypes.fsharp.lexer
8 JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util1
9 JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil1
10 JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil1
11 com.jetbrains.rider.ideaInterop.fileTypes.fsharp.highlighting1
12 com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi1
13 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion1222
14 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext1
15 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Daemon.Highlightings31
16 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil2
17 JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing2111
18 JetBrains.ReSharper.Plugins.FSharp.Psi.Util.OpensUtil112
19 com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl118
20 com.jetbrains.rider.plugins.fsharp.services.fsi2
21 JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages1361
22 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.OverrideMemberRule11
23 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FSharpNamingService111
24 JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil1
25 JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil1
26 JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer6162
27 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Generate.GenerateOverrides11
28 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions142
29 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo1111
30 JetBrains.ReSharper.Plugins.FSharp.Settings341
31 JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem221
32 JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts41212111
33 JetBrains.ReSharper.Plugins.FSharp.Services.Formatter21112
34 JetBrains.ReSharper.Plugins.FSharp.ProjectModel221
35 JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders11122
36 JetBrains.ReSharper.Plugins.FSharp.Checker2367121111
37 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules1114211
38 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi2121
39 JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers331
40 JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader3131111
Uses a module listed above itPart of a loopThe module itself
1 DocumentRangeExtensions2 FSharpFileSystemPathExtensions3 JetBrains.ReSharper.Plugins.FSharp.Checker.FcsCheckerService4 JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers.Util5 JetBrains.ReSharper.Plugins.FSharp.Psi.Features6 JetBrains.ReSharper.Plugins.FSharp.Util.SettingsStoreUtil7 com.jetbrains.rider.ideaInterop.fileTypes.fsharp.lexer8 JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util9 JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil10 JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil11 com.jetbrains.rider.ideaInterop.fileTypes.fsharp.highlighting12 com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi13 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion14 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext15 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Daemon.Highlightings16 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil17 JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing18 JetBrains.ReSharper.Plugins.FSharp.Psi.Util.OpensUtil19 com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl20 com.jetbrains.rider.plugins.fsharp.services.fsi21 JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages22 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.OverrideMemberRule23 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FSharpNamingService24 JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil25 JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil26 JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer27 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Generate.GenerateOverrides28 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions29 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo30 JetBrains.ReSharper.Plugins.FSharp.Settings31 JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem32 JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts33 JetBrains.ReSharper.Plugins.FSharp.Services.Formatter34 JetBrains.ReSharper.Plugins.FSharp.ProjectModel35 JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders36 JetBrains.ReSharper.Plugins.FSharp.Checker37 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules38 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi39 JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers40 JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReaderDocumentRangeExtensions1FSharpFileSystemPathExtensions2JetBrains.ReSharper.Plugins.FSharp.Checker.FcsCheckerService3JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers.Util4JetBrains.ReSharper.Plugins.FSharp.Psi.Features5JetBrains.ReSharper.Plugins.FSharp.Util.SettingsStoreUtil6com.jetbrains.rider.ideaInterop.fileTypes.fsharp.lexer7JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util8JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil9JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil10com.jetbrains.rider.ideaInterop.fileTypes.fsharp.highlighting11com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi12JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion13JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext14JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Daemon.Highlightings15JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil16JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing17JetBrains.ReSharper.Plugins.FSharp.Psi.Util.OpensUtil18com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl19com.jetbrains.rider.plugins.fsharp.services.fsi20JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages21JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.OverrideMemberRule22JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FSharpNamingService23JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil24JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil25JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer26JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Generate.GenerateOverrides27JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions28JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo29JetBrains.ReSharper.Plugins.FSharp.Settings30JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem31JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts32JetBrains.ReSharper.Plugins.FSharp.Services.Formatter33JetBrains.ReSharper.Plugins.FSharp.ProjectModel34JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders35JetBrains.ReSharper.Plugins.FSharp.Checker36JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules37JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi38JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers39JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader401111112221312211111211821361111111161621114211113412214121211121112221111222367121111111421121213313131111+233 more modules (most-connected shown)

At a glance — Code Health · 29% · Weak · gated by D17, X5 ·

At a glance — Architecture · 100% · Exemplary ·

At a glance — Maturity · 58% · Adequate · gated by M2 ·

At a glance — Readiness · 48% · Weak · gated by D13, P3 ·

At a glance — Security · 42% · Weak · gated by D44 ·

At a glance — Performance · 100% · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A07:2025 — Authentication Failures12High / Critical
A05:2025 — Injection9High / Critical

Roadmap

Top priorities: Resolve the 11 NoWarnInCsproj finding(s) in Explicit Debt — start with FSharp.Fantomas.Host.csproj (2), FSharp.TypeProviders.Host.NetCore.csproj (2), FSharp.Debugger.csproj; Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`; Resolve the 6 Leaked secret finding(s) in Secret Scanning — start with REDACTED (5), REDACTED.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Resolve the 11 NoWarnInCsproj finding(s) in Explicit Debt — start with FSharp.Fantomas.Host.csproj (2), FSharp.TypeProviders.Host.NetCore.csproj (2), FSharp.Debugger.csproj.+12.3 ptsMediumExplicit Debt
Resolve the 6 Leaked secret finding(s) in Secret Scanning — start with REDACTED (5), REDACTED.+4.4 ptsLowSecret Scanning
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.+8.5 ptsMediumNullable reference types
Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with ExemptFromZoningValidation.cs.+3.9 ptsLowExplicit Debt
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with FSharp.Fantomas.Host.csproj.+3.3 ptsLowADR Quality
Resolve the 6 High secret finding(s) in Secrets (history) — start with REDACTED (5), REDACTED.+3.2 ptsLowSecrets (history)
Resolve the 10 End-of-life runtime finding(s) in Platform End-of-Life — start with CoreConsoleApp.fsproj (2), ClassLibrary1.fsproj, TypeProviderLibrary.fsproj.+3.7 ptsMediumPlatform End-of-Life
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED.+1.7 ptsLowStatic Analysis (SAST)

File quality

Per-file score 0–10 — a quality signature. Of 86 files carrying findings, judged against the Production bar: 1% slop · 54% mixed · 45% near-clean.

FileScoreBandWorst signal
REDACTED1.3SlopStatic Analysis (SAST): High: REDACTED
ReSharper.FSharp/src/FSharp.TypeProviders.Host/FSharp.TypeProviders.Host.NetCore/FSharp.TypeProviders.Host.NetCore.csproj4.3MixedExplicit Debt: NoWarnInCsproj
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED
ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/ForPostfixTemplate.fs5.9MixedCode Duplication: Duplicated block (11 lines × 2)
ReSharper.FSharp/src/FSharp.Fantomas.Host/FSharp.Fantomas.Host.csproj5.9MixedExplicit Debt: NoWarnInCsproj
ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Parsing/FSharpImplTreeBuilder.fs7.1MixedGod Classes: FileTooLong: Parsing/FSharpImplTreeBuilder.fs
REDACTED7.2MixedStatic Analysis (SAST): High: REDACTED
REDACTED7.2MixedStatic Analysis (SAST): High: REDACTED
ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/FSharpTypingAssist.fs7.4MixedGod Classes: FileTooLong: src/FSharpTypingAssist.fs
ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateLambdaRule.fs7.4MixedCode Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens)
ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportModuleMemberRule.fs7.4MixedCode Duplication: Duplicated block (12–13 lines × 2)
ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateMatchExprPatternsRule.fs7.4MixedCode Duplication: Duplicated block (11 lines × 2)
ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportExtensionMemberRule.fs7.4MixedCode Duplication: Duplicated block (6 lines × 2)
ReSharper.FSharp/src/FSharp.Debugger/FSharp.Debugger.csproj7.6MixedExplicit Debt: NoWarnInCsproj
ReSharper.FSharp/src/FSharp/FSharp.Fantomas.Protocol/FSharp.Fantomas.Protocol.csproj7.6MixedExplicit Debt: NoWarnInCsproj

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 31

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.

Serious — 125

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.

Minor — 25

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 16

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 31 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.

Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.

What we checked — 31 dimensions across the health lenses
D3D4D5D13D14D16D17D19D20D26D28D29D34D35D44AX10AX3AX5AX7AX8GD1M1M2M3M4P1P2P3P6PF3X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. 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, 170 of 181 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. 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.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic

Every finding is locatable in findings.md. Run 01a1d4b5-fe69-7f35-a5ea-6c7abfd6e0f9.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • 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 (.cs, .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 (.cs, .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.
  • D4 Code Duplication — 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 49 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .cs (28,469 lines, 40% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
  • D6 Cohesion (LCOM4) — 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. 417 of 417 class(es) with two or more methods were found, but the language model this pass loaded exposed none of their method bodies, so which method touches which field could not be seen.
  • D8 Code Coverage — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
  • D11 Test Reliability — not measured this run — 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. Test reliability NOT MEASURED: the analyzer environment could not build/run the test suite (a target framework / SDK band or targeting pack the analyzer image doesn't carry), so no test ever ran. This is OUR limitation, not a defect in the repo — it is excluded from the score. We track the analyzer-image gap so it can be closed.
  • 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: `dotnet list package` exited 1 with no output.
  • 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 a Gradle build (build.gradle/build.gradle.kts), but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Gradle 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 (145256 line(s) across the 90-day window), but no complexity could be computed for .cs, .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.
  • 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: Msbuild failed when processing the file 'ReSharper.FSharp/src/FSharp/FSharp.Psi/FSharp.Psi.csproj' with message: The SDK 'JetBrains.Toolset.MainSolution.Sdk/20200625.1.1.2' specified could not be found. ReSharper.FSharp/src/FSharp/FSharp.Psi/FSharp.Psi.csproj.
  • 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 12 deducted marker(s) and the 5.1/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (38,098 lines, 53% of production source), .cs (28,469 lines, 40% 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. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
  • D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
  • 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 (71,226 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.
  • 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. `ReSharper.FSharp/src/FSharp.Debugger/src/FSharpAsyncStepper.cs`, `ReSharper.FSharp/src/FSharp.Debugger/src/FSharpSequencePointInvokedMethodsProvider.cs`, `ReSharper.FSharp/src/FSharp.Debugger/src/FSharpUnitReturnValueFilter.cs`, `ReSharper.FSharp/src/FSharp/FSharp.ProjectModelBase/src/FSharpAsyncUtil.cs`, `ReSharper.FSharp/src/FSharp/FSharp.ProjectModelBase/src/FSharpZones.cs`, … (+94 more) 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.
  • D43 Malicious Dependencies — 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. Osv: osv-scanner exited 127 with no findings — dependency CVEs were not measured. 'osv-scanner' exited 127 and produced no findings, and that exit code has no documented repo-side meaning — so this run measured nothing, and nothing here is a statement about the repository.
  • AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
  • AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: 1 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
  • 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.
  • 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.
  • X23 Unguarded diagnostic materialisation — 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.
  • Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for ReSharper.FSharp/src/FSharp/FSharp.Psi/FSharp.Psi.csproj, ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/FSharp.Psi.Features.fsproj, ReSharper.FSharp/src/FSharp/FSharp.Common/FSharp.Common.fsproj, ReSharper.FSharp/src/FSharp/FSharp.ProjectModelBase/FSharp.ProjectModelBase.csproj, ReSharper.FSharp/test/src/FSharp.Tests/FSharp.Tests.fsproj and 14 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.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

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

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • 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.
  • 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.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • 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.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: 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.
  • 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 Classes8.9 / 10Strong✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented → Verified → Prevented · effective 8.9 / 10 · rule-coverage 100% · ceiling Prevented

22 god class(es) detected.

FileTooLong: AssemblyReader/ProjectFcsModuleReader.fs · ×10ReSharper.FSharp/src/FSharp/FSharp.Common/src/Shim/AssemblyReader/ProjectFcsModuleReader.fs
TooManyMethods: ProjectFcsModuleReader · ×7ReSharper.FSharp/src/FSharp/FSharp.Common/src/Shim/AssemblyReader/ProjectFcsModuleReader.fs:138
TooManyFunctions: PsiUtil · ×3ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/PsiUtil.fs:2
ClassTooLong: FSharpEnterHandlerDelegate · ×2rider-fsharp/src/main/java/com/jetbrains/rider/plugins/fsharp/editorActions/FSharpEnterHandlerDelegate.kt:33

What to do

  1. Resolve the 10 FileTooLong finding(s) in God Classes — start with ProjectFcsModuleReader.fs, FSharpTypingAssist.fs, FSharpImplTreeBuilder.fs. — One of this dimension's main actionable groups (10 warning-level).
  2. Resolve the 7 TooManyMethods finding(s) in God Classes — start with ProjectFcsModuleReader.fs, FSharpTreeBuilderBase.fs, FSharpTypingAssist.fs. — One of this dimension's main actionable groups (7 warning-level).
  3. Resolve the 3 TooManyFunctions finding(s) in God Classes — start with PsiUtil.fs, FcsErrorsStageProcessBase.fs, FSharpHighlightingAttributeIds.fs. — One of this dimension's main actionable groups (3 warning-level).

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

D4 · Code Duplication9.7 / 10Stronggated by 63 serious findings✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.7 / 10 · rule-coverage 100% · ceiling Verified

49 duplicated block group(s) detected. A further 14 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. Measured on part of this repository only: .cs (40% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.

Duplicated block (5 lines × 2) · ×12ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/AppExpressionAnalyzer.fs:5
Duplicated block (7 lines × 2) · ×6ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Debugger/FSharpSourceCallableExpressionsProvider.fs:262
Duplicated block (6 lines × 2) · ×5ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/RedundantQualifierAnalyzer.fs:8
Duplicated block (5 lines × 3) · ×4ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/RedundantQualifierAnalyzer.fs:7
Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateLambdaRule.fs:1

+ 25 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 12 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with AppExpressionAnalyzer.fs, AsPatAnalyzer.fs, IndexerExprAnalyzer.fs. — One of this dimension's main actionable groups (12 warning-level).
  2. Resolve the 6 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with FSharpSourceCallableExpressionsProvider.fs, FSharpTypingAssist.fs, FSharpImplTreeBuilder.fs. — One of this dimension's main actionable groups (6 warning-level).
  3. Resolve the 5 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with RedundantQualifierAnalyzer.fs, ImportExtensionMemberRule.fs, FSharpInternalActionGroup.fs. — One of this dimension's main actionable groups (5 warning-level).

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

10 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D13 · Secret Scanning0.0 / 10Critical✓ Tool-verified

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Prevented

6 secret(s) detected.

REDACTED

What to do

  1. Resolve the 6 Leaked secret finding(s) in Secret Scanning — start with REDACTED (5), REDACTED. — One of this dimension's main actionable groups (6 issue-level).

Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 101 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 32 direct `PackageReference`(s), and 76 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 a Gradle build (build.gradle/build.gradle.kts), 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.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D16 · Bus Factor8.7 / 10Strong✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

Maturity: Documented → Verified → Prevented · effective 8.7 / 10 · rule-coverage 100% · ceiling Documented

42 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is ReSharper.FSharp/src/FSharp/FSharp.Common/src/Shim/AssemblyReader/ProjectFcsModuleReader.fs. Counted over 327 of the 1005 production source files in this repository: 674 are under the ~2,400-byte size floor this dimension measures over, and the remaining 4 have no attributable history left to measure.

Off-boarding risk: anonymized user #1 · ×3
Further sole-owners (lower concentration)

What to do

  1. Resolve the 3 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (3 recommendation-level).
  2. Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.

D17 · Explicit Debt0.0 / 10Critical✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Prevented

12 deducted debt markers + unmeasured dead symbols across 186 LoC in the .NET projects (5.1/KLoC) → score 0.0. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs, .cs (93% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).

NoWarnInCsproj · ×11ReSharper.FSharp/src/FSharp.Debugger/FSharp.Debugger.csproj:13
FixmeCommentReSharper.FSharp/src/FSharp.RiderPlugin/src/Install/ExemptFromZoningValidation.cs:13

What to do

  1. Resolve the 11 NoWarnInCsproj finding(s) in Explicit Debt — start with FSharp.Fantomas.Host.csproj (2), FSharp.TypeProviders.Host.NetCore.csproj (2), FSharp.Debugger.csproj. — One of this dimension's main actionable groups (11 issue-level).
  2. Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with ExemptFromZoningValidation.cs. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

2 of 2 documentation facets pass in full. 2 document(s) read across 11 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs foundReSharper.FSharp/src/FSharp.Fantomas.Host/FSharp.Fantomas.Host.csproj:16

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with FSharp.Fantomas.Host.csproj. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.

D26 · Project Cohesion10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 of 10 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

D28 · Secrets (history)4.0 / 10Weak✓ Tool-verified

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented → Verified → Prevented · effective 4.0 / 10 · rule-coverage 100% · ceiling Documented

6 finding(s): 0 critical, 6 high, 0 medium, 0 low.

REDACTED

What to do

  1. Resolve the 6 High secret finding(s) in Secrets (history) — start with REDACTED (5), REDACTED. — One of this dimension's main actionable groups (6 issue-level).

Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.

D29 · Static Analysis (SAST)6.7 / 10Adequate✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

Maturity: Documented → Verified → Prevented · effective 6.7 / 10 · rule-coverage 100% · ceiling Documented

9 finding(s): 0 critical, 8 high, 1 medium, 0 low. 6 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 98 file(s) — `ReSharper.FSharp/src/FSharp.Debugger/src/FSharpAsyncStepper.cs` (line 27), `ReSharper.FSharp/src/FSharp.Debugger/src/FSharpSequencePointInvokedMethodsProvider.cs` (line 21), `ReSharper.FSharp/src/FSharp.Debugger/src/FSharpUnitReturnValueFilter.cs` (line 10), `ReSharper.FSharp/src/FSharp/FSharp.ProjectModelBase/src/FSharpAsyncUtil.cs` (lines 189–209), `ReSharper.FSharp/src/FSharp/FSharp.ProjectModelBase/src/FSharpZones.cs` (lines 14–29), … (+93 more) — 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 70 of those file(s) — `ReSharper.FSharp/src/FSharp.Debugger/src/FSharpAsyncStepper.cs`, `ReSharper.FSharp/src/FSharp.Debugger/src/FSharpSequencePointInvokedMethodsProvider.cs`, `ReSharper.FSharp/src/FSharp.Debugger/src/FSharpUnitReturnValueFilter.cs`, `ReSharper.FSharp/src/FSharp/FSharp.Psi/src/Annotations/FSharpAnnotatedCacheProcessor.cs`, `ReSharper.FSharp/src/FSharp/FSharp.Psi/src/CodeFormatter/FSharpCodeFormatter.cs`, … (+65 more) — 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.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
  3. No action in Static Analysis (SAST) — all 6 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (6 issue-level, 0 of them charged here).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D34 · Knowledge Freshness9.8 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

Maturity: Documented → Verified → Prevented · effective 9.8 / 10 · rule-coverage 100% · ceiling Documented

8 of 331 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is ReSharper.FSharp/src/FSharp/FSharp.Psi/src/Parsing/FSharpPreprocessedLexer.cs. Counted over 331 of the 1005 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×8ReSharper.FSharp/src/FSharp/FSharp.Psi/src/Parsing/FSharpPreprocessedLexer.cs:1
Orphaned files with no living knowledge

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.

D35 · Change Coupling10.0 / 10Stronggated by 3 serious findings✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: ForPostfixTemplate.fs↔MatchPostfixTemplate.fs 55%; ClassPart.cs↔FSharpImplUtil.cs 54%; FsiHost.fs↔SandboxDocumentLanguageSupportFSharpScript.fs 50%

Change coupling: ForPostfixTemplate.fs ↔ MatchPostfixTemplate.fs · ×3ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/ForPostfixTemplate.fs:1

What to do

  1. Resolve the 3 Change coupling finding(s) in Change Coupling — start with ForPostfixTemplate.fs, ClassPart.cs, FsiHost.fs. — One of this dimension's main actionable groups (3 warning-level).

Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.

D44 · Platform End-of-Life2.0 / 10Critical✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

Maturity: Documented → Verified → Prevented · effective 2.0 / 10 · rule-coverage 100% · ceiling Documented

3 end-of-life runtime(s) and 0 end-of-life framework(s), read from 80 platform declaration(s) and 4 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.

End-of-life runtime: .NET net5.0 · ×10rider-fsharp/src/test/testData/solutions/SplitNestedWithFile/ClassLibrary1/ClassLibrary1.fsproj:3

What to do

  1. Resolve the 10 End-of-life runtime finding(s) in Platform End-of-Life — start with CoreConsoleApp.fsproj (2), ClassLibrary1.fsproj, TypeProviderLibrary.fsproj. — One of this dimension's main actionable groups (10 warning-level).

Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX10 · Code composition10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

AX7 · Slice cohesion10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether feature slices stay independent (no direct cross-slice references) — the discipline that makes vertical-slice architecture pay off.

Method: Roslyn scan (vertical-slice gated): feature slices resolved from namespaces (.Features.*, .Slices.*) or project names; cross-slice type references detected. Deterministic, traceable.

AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

GD1 · Unfinished & placeholder code9.9 / 10Exemplary✓ Tool-verified

Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

  • A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface. (×23) — ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/FSharpStringLexer.fs:69, ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/FSharpStringLexer.fs:108, ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/FSharpStringLexer.fs:179, …

What to do

  • Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
M1 · Documentation (README)6.7 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

P2 · Observability6.5 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • Only 5/6 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `rider-fsharp/projectTemplates/FSharpConsoleApplicationTemplate`.

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

  • No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
  • `ReSharper.FSharp/Directory.Build.props` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — ReSharper.FSharp/Directory.Build.props:17

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.
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

X5 · Nullable reference types2.0 / 10Critical✓ Tool-verified

Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • 0/2 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.

What to do

  • Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health29%Weak — gated by D17, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture100%ExemplarySolid.
Maturity58%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness48%Weak — gated by D13, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security42%Weak — gated by D44Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100%ExemplaryStrongest area.
Unscored — 3 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
  • SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 81 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AC1 Text alternatives — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AX1 Captive dependencies — no DI registrations detected
  • AX2 Stateful singletons — no singleton implementations detected
  • AX4 Dependency direction — not applicable to a vertical-slice architecture (the inward-dependency rule is for layered/clean styles)
  • AX6 Interface segregation — AX6 reached only 41% of this repository's production lines — fsharp (38,098 lines), kotlin (4,142 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C2 Access Controls — 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 — .cs, .fs exposed no member bodies
  • D10 Test Quality — ~51094 lines of test source are present (.fs, .kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
  • D11 Test Reliability — Test reliability not measured — analyzer environment
  • D12 Dependency Hygiene — Dependency hygiene not measured
  • D15 Churn × Complexity Hotspots — complexity unreadable for .cs, .fs — churn × complexity hotspots could not be measured
  • D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .fs, .java, .kt, 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 — .cs, .fs exposed no member bodies
  • D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; F#, Java, Kotlin not measured.
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • 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, .java, .kt source were not judged.
  • D25 ADR Conformance — no ADRs to check
  • D27 Navigability — No calls could be sampled, so navigability was not assessed — tracing effort is measured over resolved call sites and this target exposed none. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
  • D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan; nuget packages.config: osv-scanner exited 127 with no findings — dependency CVEs were not measured
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — 99 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.
  • D43 Malicious Dependencies — Scanner failed to run — not a clean result
  • D6 Cohesion (LCOM4) — cohesion (LCOM4) not measured — the code model exposed no member bodies
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — no coverage collector is wired up
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (34 value object(s))
  • 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 40% of this repository's production lines — fsharp (38,098 lines), kotlin (4,142 lines), java (517 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 — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P7 Outbound HTTP resilience — not 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.
  • 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X12 Unreachable branch — X12 reached only 40% of this repository's production lines — fsharp (38,098 lines), kotlin (4,142 lines), java (517 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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 — no async method does work a token could cancel
  • X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X21 Side-effecting pattern guard — 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — X23 reached only 40% of this repository's production lines — fsharp (38,098 lines), kotlin (4,142 lines), java (517 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X28 Index access outside its own emptiness guard — X28 reached only 40% of this repository's production lines — fsharp (38,098 lines), kotlin (4,142 lines), java (517 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 31 finding(s)
D17 · Explicit Debt · NoWarnInCsproj · ×11
  • NoWarnInCsproj ReSharper.FSharp/src/FSharp.Debugger/FSharp.Debugger.csproj:13 — MSB3277 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.
  • NoWarnInCsproj ReSharper.FSharp/src/FSharp.Fantomas.Host/FSharp.Fantomas.Host.csproj:15 — MSB3277 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.
  • NoWarnInCsproj ReSharper.FSharp/src/FSharp/FSharp.Fantomas.Protocol/FSharp.Fantomas.Protocol.csproj:12 — MSB3277 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.
  • NoWarnInCsproj ReSharper.FSharp/src/FSharp/FSharp.ProjectModelBase/FSharp.ProjectModelBase.csproj:12 — MSB3277 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.
  • NoWarnInCsproj ReSharper.FSharp/src/FSharp/FSharp.Psi/FSharp.Psi.csproj:12 — MSB3277 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.
  • NoWarnInCsproj ReSharper.FSharp/src/FSharp/FSharp.TypeProviders.Protocol/FSharp.TypeProviders.Protocol.csproj:12 — MSB3277 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.
  • NoWarnInCsproj ReSharper.FSharp/src/FSharp.TypeProviders.Host/FSharp.TypeProviders.Host/FSharp.TypeProviders.Host.csproj:15 — MSB3277 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.
  • NoWarnInCsproj ReSharper.FSharp/src/FSharp.TypeProviders.Host/FSharp.TypeProviders.Host.NetCore/FSharp.TypeProviders.Host.NetCore.csproj:14 — MSB3277 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.
  • NoWarnInCsproj ReSharper.FSharp/src/FSharp.RiderPlugin/proj/src/FSharp.RiderPlugin.csproj:12 — MSB3277 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.
  • NoWarnInCsproj ReSharper.FSharp/src/FSharp.Fantomas.Host/FSharp.Fantomas.Host.csproj:15 — NU1701 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.
  • NoWarnInCsproj ReSharper.FSharp/src/FSharp.TypeProviders.Host/FSharp.TypeProviders.Host.NetCore/FSharp.TypeProviders.Host.NetCore.csproj:14 — NU1701 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.
D13 · Secret Scanning · Leaked secret · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D28 · Secrets (history) · High secret · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
Serious — 125 finding(s)
GD1 · Unfinished & placeholder code · Unfinished stub · ×23
  • Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/FSharpStringLexer.fs:69 — A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/FSharpStringLexer.fs:108 — A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/FSharpStringLexer.fs:179 — A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/FSharpStringLexer.fs:202 — A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/FSharpInlineVariable.fs:25 — A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/FSharpInlineVariable.fs:26 — A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/FSharpInlineVariable.fs:27 — A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/FSharpInlineVariable.fs:28 — A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/FSharpInlineVariable.fs:29 — A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/FSharpInlineVariable.fs:30 — A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/FSharpInlineVariable.fs:31 — A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/FSharpInlineVariable.fs:32 — A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/FSharpInlineVariable.fs:33 — A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/FSharpInlineVariable.fs:34 — A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/FSharpInlineVariable.fs:35 — A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/FSharpInlineVariable.fs:36 — A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/FSharpInlineVariable.fs:37 — A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/FSharpInlineVariable.fs:38 — A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ImportMemberFix.fs:99 — A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Search/FSharpPathReference.fs:73 — A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Search/FSharpPathReference.fs:74 — A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Search/FSharpPathReference.fs:75 — A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Common/src/ProjectModel/FSharpLanguageLevelProvider.fs:190 — A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×12
  • Duplicated block (5 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/AppExpressionAnalyzer.fs:5 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/AppExpressionAnalyzer.fs:5-9 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/Intentions/ConvertPartiallyAppliedFunctionToLambdaAction.fs:8-12 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (5 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/AsPatAnalyzer.fs:1 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/AsPatAnalyzer.fs:1-5 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/RedundantParenTypeUsageAnalyzer.fs:1-5 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/IndexerExprAnalyzer.fs:1 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/IndexerExprAnalyzer.fs:1-5 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/RedundantParenPatAnalyzer.fs:1-5 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/RecursiveInvocationAnalyzer.fs:1 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/RecursiveInvocationAnalyzer.fs:1-5 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/RedundantNew.fs:1-5 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateMatchExprPatternsRule.fs:1 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateMatchExprPatternsRule.fs:1-5 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImplementInterfaceMemberRule.fs:1-5 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/ForPostfixTemplate.fs:9 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/ForPostfixTemplate.fs:9-13 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/WithPostfixTemplate.fs:7-11 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/NewObjPostfixTemplate.fs:1 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/NewObjPostfixTemplate.fs:1-5 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/NotTemplate.fs:1-5 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/Intentions/InvertIfAction.fs:1 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/Intentions/InvertIfAction.fs:1-5 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/Intentions/ToLiteralAction.fs:1-5 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemovePatternArgumentFix.fs:5 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemovePatternArgumentFix.fs:5-9 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ReplaceWithWildPatFix.fs:9-13 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ReplaceLetWithExpressionFix.fs:1 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ReplaceLetWithExpressionFix.fs:1-5 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ToStaticMemberFix.fs:1-5 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ReplaceWithAbbreviatedTypeFix.fs:8 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ReplaceWithAbbreviatedTypeFix.fs:8-12 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/FSharpNamingService.fs:11-16 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (5 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Stages/InferredTypeCodeVisionProvider.fs:12 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Stages/InferredTypeCodeVisionProvider.fs:12-16 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Stages/PipeChainTypeHintStage.fs:13-17 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D3 · God Classes · FileTooLong · ×10
  • FileTooLong: AssemblyReader/ProjectFcsModuleReader.fs ReSharper.FSharp/src/FSharp/FSharp.Common/src/Shim/AssemblyReader/ProjectFcsModuleReader.fs — FileTooLong — 1617 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1117 over it, 3.23× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/FSharpTypingAssist.fs ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/FSharpTypingAssist.fs — FileTooLong — 1468 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 968 over it, 2.94× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Parsing/FSharpImplTreeBuilder.fs ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Parsing/FSharpImplTreeBuilder.fs — FileTooLong — 1282 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 782 over it, 2.56× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: ProjectItems/FSharpItemsContainer.fs ReSharper.FSharp/src/FSharp/FSharp.Common/src/ProjectModel/Host/ProjectItems/FSharpItemsContainer.fs — FileTooLong — 1182 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 682 over it, 2.36× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: ParameterInfo/FSharpParameterInfo.fs ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/ParameterInfo/FSharpParameterInfo.fs — FileTooLong — 1013 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 513 over it, 2.03× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Util/MatchTree.fs ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/MatchTree.fs — FileTooLong — 997 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 497 over it, 1.99× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Parsing/FSharpTreeBuilderBase.fs ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Parsing/FSharpTreeBuilderBase.fs — FileTooLong — 845 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 345 over it, 1.69× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Generate/GenerateOverrides.fs ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Generate/GenerateOverrides.fs — FileTooLong — 581 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 33 functions. The bar is 500 significant lines; this is 81 over it, 1.16× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Refactorings/IntroduceVariable.fs ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/IntroduceVariable.fs — FileTooLong — 566 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 66 over it, 1.13× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: editorActions/FSharpEnterHandlerDelegate.kt rider-fsharp/src/main/java/com/jetbrains/rider/plugins/fsharp/editorActions/FSharpEnterHandlerDelegate.kt — FileTooLong — 526 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: FSharpEnterHandlerDelegate (33-748). The bar is 500 significant lines; this is 26 over it, 1.05× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
D44 · Platform End-of-Life · End-of-life runtime · ×10
  • End-of-life runtime: .NET net5.0 rider-fsharp/src/test/testData/solutions/SplitNestedWithFile/ClassLibrary1/ClassLibrary1.fsproj:3 — rider-fsharp/src/test/testData/solutions/SplitNestedWithFile/ClassLibrary1/ClassLibrary1.fsproj declares .NET net5.0 as this project's target framework, and .NET 5, support ended 2022-05-10. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2022-05-10 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/ConsoleAppTwoTargetFrameworks/CoreConsoleApp.fsproj:5 — rider-fsharp/src/test/testData/solutions/ConsoleAppTwoTargetFrameworks/CoreConsoleApp.fsproj declares .NET net6.0 as this project's target framework, and .NET 6 LTS, support ended 2024-11-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-11-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/CoreConsoleApp/CoreConsoleApp.fsproj:5 — rider-fsharp/src/test/testData/solutions/CoreConsoleApp/CoreConsoleApp.fsproj declares .NET net6.0 as this project's target framework, and .NET 6 LTS, support ended 2024-11-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-11-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/CsvTypeProvider/TypeProviderLibrary/TypeProviderLibrary.fsproj:4 — rider-fsharp/src/test/testData/solutions/CsvTypeProvider/TypeProviderLibrary/TypeProviderLibrary.fsproj declares .NET net6.0 as this project's target framework, and .NET 6 LTS, support ended 2024-11-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-11-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/FableApp/FableApp.fsproj:5 — rider-fsharp/src/test/testData/solutions/FableApp/FableApp.fsproj declares .NET net6.0 as this project's target framework, and .NET 6 LTS, support ended 2024-11-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-11-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/ReferencesOrder/ReferencesOrder.fsproj:5 — rider-fsharp/src/test/testData/solutions/ReferencesOrder/ReferencesOrder.fsproj declares .NET net6.0 as this project's target framework, and .NET 6 LTS, support ended 2024-11-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-11-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/SwaggerProviderCSharp/CSharpLibrary/CSharpLibrary.csproj:4 — rider-fsharp/src/test/testData/solutions/SwaggerProviderCSharp/CSharpLibrary/CSharpLibrary.csproj declares .NET net6.0 as this project's target framework, and .NET 6 LTS, support ended 2024-11-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-11-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/SwaggerProviderCSharp/SwaggerProviderLibrary/SwaggerProviderLibrary.fsproj:5 — rider-fsharp/src/test/testData/solutions/SwaggerProviderCSharp/SwaggerProviderLibrary/SwaggerProviderLibrary.fsproj declares .NET net6.0 as this project's target framework, and .NET 6 LTS, support ended 2024-11-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-11-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET netcoreapp3.1 ReSharper.FSharp/src/FSharp.TypeProviders.Host/FSharp.TypeProviders.Host.NetCore/FSharp.TypeProviders.Host.NetCore.csproj:18 — ReSharper.FSharp/src/FSharp.TypeProviders.Host/FSharp.TypeProviders.Host.NetCore/FSharp.TypeProviders.Host.NetCore.csproj declares .NET netcoreapp3.1 as this project's target framework, and .NET Core 3.1 LTS, support ended 2022-12-13. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2022-12-13 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET netcoreapp3.1 rider-fsharp/src/test/testData/solutions/FormatCodeApp/FormatCodeApp/FormatCodeApp.fsproj:5 — rider-fsharp/src/test/testData/solutions/FormatCodeApp/FormatCodeApp/FormatCodeApp.fsproj declares .NET netcoreapp3.1 as this project's target framework, and .NET Core 3.1 LTS, support ended 2022-12-13. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2022-12-13 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
D3 · God Classes · TooManyMethods · ×7
  • TooManyMethods: ProjectFcsModuleReader ReSharper.FSharp/src/FSharp/FSharp.Common/src/Shim/AssemblyReader/ProjectFcsModuleReader.fs:138 — TooManyMethods — 173 methods. The bar is 30 methods; this is 143 over it, 5.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: FSharpTreeBuilderBase ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Parsing/FSharpTreeBuilderBase.fs:25 — TooManyMethods — 76 methods. The bar is 30 methods; this is 46 over it, 2.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: FSharpTypingAssist ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/FSharpTypingAssist.fs:35 — TooManyMethods — 73 methods. The bar is 30 methods; this is 43 over it, 2.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: FSharpElementFactory ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/LanguageService/FSharpElementFactory.fs:20 — TooManyMethods — 58 methods. The bar is 30 methods; this is 28 over it, 1.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ProjectMapping ReSharper.FSharp/src/FSharp/FSharp.Common/src/ProjectModel/Host/ProjectItems/FSharpItemsContainer.fs:421 — TooManyMethods — 48 methods. The bar is 30 methods; this is 18 over it, 1.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: FcsProjectProvider ReSharper.FSharp/src/FSharp/FSharp.Common/src/Checker/FcsProjectProvider.fs:71 — TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: FSharpExpressionTreeBuilder ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Parsing/FSharpImplTreeBuilder.fs:713 — TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×6
  • Duplicated block (7 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Debugger/FSharpSourceCallableExpressionsProvider.fs:262 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Debugger/FSharpSourceCallableExpressionsProvider.fs:262-268 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Debugger/FSharpSourceCallableExpressionsProvider.fs:311-317 — 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.
  • Duplicated block (7 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/FSharpTypingAssist.fs:1046 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/FSharpTypingAssist.fs:1046-1052 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/FSharpTypingAssist.fs:1214-1220 — 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.
  • Duplicated block (7 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Parsing/FSharpImplTreeBuilder.fs:164 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Parsing/FSharpImplTreeBuilder.fs:164-170 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Parsing/FSharpSigTreeBuilder.fs:123-129 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/Intentions/ElifToIfAction.fs:4 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/Intentions/ElifToIfAction.fs:4-10 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/Intentions/IfToElifAction.fs:4-10 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/Intentions/IfToElifAction.fs:7 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/Intentions/IfToElifAction.fs:7-13 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ConvertTupleToArrayOrListElementsFix.fs:8-14 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (7 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/UpdateRecordFieldTypeInSignatureFix.fs:1 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/UpdateRecordFieldTypeInSignatureFix.fs:1-7 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/UpdateRecordFieldsInSignatureFix.fs:1-7 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×5
  • Duplicated block (6 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/RedundantQualifierAnalyzer.fs:8 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/RedundantQualifierAnalyzer.fs:8-13 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/FSharpExpressionUtil.fs:10-15 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (6 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportExtensionMemberRule.fs:56 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportExtensionMemberRule.fs:56-61 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportStaticMemberRule.fs:68-73 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportExtensionMemberRule.fs:56` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Internal/FSharpInternalActionGroup.fs:21 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Internal/FSharpInternalActionGroup.fs:21-26 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Internal/FSharpInternalActionGroup.fs:55-60 — 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.
  • Duplicated block (6 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/MatchPostfixTemplate.fs:37 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/MatchPostfixTemplate.fs:37-43 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/NotTemplate.fs:28-33 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/MatchPostfixTemplate.fs:37` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ChangeTypeFix.fs:14 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ChangeTypeFix.fs:14-19 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/SpecifyParameterBaseTypeFix.fs:10-15 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×4
  • Duplicated block (5 lines × 3) ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/RedundantQualifierAnalyzer.fs:7 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/RedundantQualifierAnalyzer.fs:7-11 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/ParameterInfo/FSharpParameterInfo.fs:23-27 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/FSharpExpressionUtil.fs:9-13 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (5 lines × 3) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateLambdaRule.fs:19 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateLambdaRule.fs:19-23 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/NameSuggestionRule.fs:15-19 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ToRecursiveFunctionRule.fs:15-19 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
  • Duplicated block (5 lines × 3) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportModuleMemberRule.fs:46 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportModuleMemberRule.fs:46-50 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportTypeElementRule.fs:96-100 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/OverrideMemberRule.fs:50-56 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (5 lines × 3) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/ForPostfixTemplate.fs:143 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/ForPostfixTemplate.fs:143-148 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/MatchPostfixTemplate.fs:42-47 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/NotTemplate.fs:32-36 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/ForPostfixTemplate.fs:143` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D3 · God Classes · TooManyFunctions · ×3
  • TooManyFunctions: PsiUtil ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/PsiUtil.fs:2 — TooManyFunctions — 66 functions. The bar is 30 functions; this is 36 over it, 2.20× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: FSharpErrors ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Stages/FcsErrorsStageProcessBase.fs:40 — TooManyFunctions — 65 functions. The bar is 30 functions; this is 35 over it, 2.17× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: FSharpHighlightingAttributeIds ReSharper.FSharp/src/FSharp/FSharp.Common/src/Util/FSharpHighlightingAttributeIds.fs:12 — TooManyFunctions — 48 functions. The bar is 30 functions; this is 18 over it, 1.60× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
D35 · Change Coupling · Change coupling · ×3
  • Change coupling: ForPostfixTemplate.fs ↔ MatchPostfixTemplate.fs ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/ForPostfixTemplate.fs:1 — `ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/ForPostfixTemplate.fs` and `ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/MatchPostfixTemplate.fs` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `60e79192` Compleion/postfix: add 'new' for record types; `d9b48773` Completion/postfix: enable 'for', 'match' (at that commit the files were still `ReSharper.FSharp/src/FSharp.Psi.Features/src/PostfixTemplates/ForPostfixTemplate.fs` and `ReSharper.FSharp/src/FSharp.Psi.Features/src/PostfixTemplates/MatchPostfixTemplate.fs`); `68f7bb9f` Completion: add 'match' postfix template, add branch generation (at that commit the files were still `ReSharper.FSharp/src/FSharp.Psi.Features/src/PostfixTemplates/ForPostfixTemplate.fs` and `ReSharper.FSharp/src/FSharp.Psi.Features/src/PostfixTemplates/MatchPostfixTemplate.fs`) — run `git show` on any of them.
  • Change coupling: ClassPart.cs ↔ FSharpImplUtil.cs ReSharper.FSharp/src/FSharp/FSharp.Psi/src/Impl/Cache2/Parts/ClassPart.cs:1 — `ReSharper.FSharp/src/FSharp/FSharp.Psi/src/Impl/Cache2/Parts/ClassPart.cs` and `ReSharper.FSharp/src/FSharp/FSharp.Psi/src/Impl/FSharpImplUtil.cs` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `82e05349` Fcs/types: disambiguate type elements in-place when mapping types; `2601c01f` Psi: remove some IFSharpTypeOldDeclaration usages (at that commit the files were still `ReSharper.FSharp/src/FSharp.Psi/src/Impl/Cache2/Parts/ClassPart.cs` and `ReSharper.FSharp/src/FSharp.Psi/src/Impl/FSharpImplUtil.cs`); `37c22c2b` Specify nullability annotation when creating declared types (at that commit the files were still `ReSharper.FSharp/src/FSharp.Psi/src/Impl/Cache2/Parts/ClassPart.cs` and `ReSharper.FSharp/src/FSharp.Psi/src/Impl/FSharpImplUtil.cs`) — run `git show` on any of them.
  • Change coupling: FsiHost.fs ↔ SandboxDocumentLanguageSupportFSharpScript.fs ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Fsi/FsiHost.fs:1 — `ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Fsi/FsiHost.fs` and `ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/LanguageService/SandboxDocumentLanguageSupportFSharpScript.fs` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `f8190966` Rename Full to `Just ordinary` zones to; `7f9e82f1` light and full zones; `81babf6c` Cleanup — run `git show` on any of them.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3
  • Members sharing a duplicated core (4 members, 50+ identical tokens) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateLambdaRule.fs:1 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateLambdaRule.fs:1-144 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportModuleMemberRule.fs:1-163 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportTypeElementRule.fs:1-251 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/NameSuggestionRule.fs:1-171 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/NameSuggestionRule.fs:1 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/NameSuggestionRule.fs:1-171 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/NamedArgumentsRule.fs:1-245 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/RecordFieldRule.fs:1-180 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/UnionCaseFieldsRule.fs:1-169 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ImportMemberFix.fs:1 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ImportMemberFix.fs:1-285 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/IntroduceVariable.fs:1-770 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/Deconstruction.fs:1-429 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/MatchTree.fs:1-1331 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×3
  • Duplicated block (11 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateMatchExprPatternsRule.fs:76 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateMatchExprPatternsRule.fs:76-86 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/UnionCaseFieldsRule.fs:59-69 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (11 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Parsing/FSharpImplTreeBuilder.fs:640 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Parsing/FSharpImplTreeBuilder.fs:640-650 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Parsing/FSharpImplTreeBuilder.fs:719-729 — 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.
  • Duplicated block (11 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/ForPostfixTemplate.fs:144 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/ForPostfixTemplate.fs:144-154 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/MatchPostfixTemplate.fs:43-53 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (5 lines × 4) · ×3
  • Duplicated block (5 lines × 4) ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/AppExpressionAnalyzer.fs:1 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/AppExpressionAnalyzer.fs:1-5 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/ExtensionAttributeAnalyzer.fs:1-5 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/RedundantBackticksAnalyzer.fs:1-5 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/RequireQualifiedAccessAttributeAnalyzer.fs:1-5 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
  • Duplicated block (5 lines × 4) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportExtensionMemberRule.fs:4 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportExtensionMemberRule.fs:4-8 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportModuleMemberRule.fs:5-9 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportStaticMemberRule.fs:4-8 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportTypeElementRule.fs:7-11 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
  • Duplicated block (5 lines × 4) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ImportMemberFix.fs:25 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ImportMemberFix.fs:25-29 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/IntroduceVariable.fs:24-28 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/Deconstruction.fs:16-20 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/MatchTree.fs:13-17 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
D3 · God Classes · ClassTooLong · ×2
  • ClassTooLong: FSharpEnterHandlerDelegate rider-fsharp/src/main/java/com/jetbrains/rider/plugins/fsharp/editorActions/FSharpEnterHandlerDelegate.kt:33 — ClassTooLong — 494 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 94 over it, 1.24× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: FSharpTokenType rider-fsharp/src/main/java/com/jetbrains/rider/ideaInterop/fileTypes/fsharp/lexer/FSharpTokenType.java:13 — ClassTooLong — 466 significant lines (blank, comment-only and punctuation-only lines excluded), 3 methods. The bar is 400 significant lines; this is 66 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Duplicated block (12–13 lines × 2) · ×2
  • Duplicated block (12–13 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportModuleMemberRule.fs:68 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportModuleMemberRule.fs:68-79 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportTypeElementRule.fs:154-166 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (12–13 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ChangeTypeFix.fs:84 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ChangeTypeFix.fs:84-96 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/FSharpChangeTypeHelper.fs:69-80 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×2
  • Duplicated block (9 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateMatchExprPatternsRule.fs:14 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateMatchExprPatternsRule.fs:14-22 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImplementInterfaceMemberRule.fs:15-23 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (9 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/IntroduceVariable.fs:21 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/IntroduceVariable.fs:21-29 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/MatchTree.fs:10-18 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×2
  • Duplicated block (6 lines × 3) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/Intentions/ElifToIfAction.fs:6 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/Intentions/ElifToIfAction.fs:6-11 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/Intentions/IfToElifAction.fs:6-11 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ConvertTupleToArrayOrListElementsFix.fs:7-12 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (6 lines × 3) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportExtensionMemberRule.fs:9 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportExtensionMemberRule.fs:9-14 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportStaticMemberRule.fs:9-14 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/NamedArgumentsRule.fs:8-13 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (4–5 lines × 4) · ×2
  • Duplicated block (4–5 lines × 4) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateLambdaRule.fs:14 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateLambdaRule.fs:14-18 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportModuleMemberRule.fs:13-17 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportTypeElementRule.fs:20-23 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/NameSuggestionRule.fs:11-14 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
  • Duplicated block (4–5 lines × 4) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/NameSuggestionRule.fs:1 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/NameSuggestionRule.fs:1-5 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/NamedArgumentsRule.fs:4-7 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/RecordFieldRule.fs:5-8 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/UnionCaseFieldsRule.fs:1-5 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
D17 · Explicit Debt · FixmeComment · ×1
  • FixmeComment ReSharper.FSharp/src/FSharp.RiderPlugin/src/Install/ExemptFromZoningValidation.cs:13 — // FIXME(k15tfu): Temporarily ignore zone validation errors for JetBrains.ReSharper.Plugins.FSharp.*. See https://youtrack.jetbrains.com/issue/RIDER-99672.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (10 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (10 members, 50+ identical tokens) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/AddExtensionAttributeFix.fs:1 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/AddExtensionAttributeFix.fs:1-51 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ConvertTupleToArrayOrListElementsFix.fs:1-38 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveIndexerDotFix.fs:1-25 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveRedundantAsPatFix.fs:1-29 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveRedundantQualifierFix.fs:1-40 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveYieldFix.fs:1-27 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ReplaceLambdaWithBuiltinFunctionFix.fs:1-36 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/SimplifyLambdaFix.fs:1-35 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ToAbstractFix.fs:1-30 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ToObjectExpressionFix.fs:1-34 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (5 members, 50+ identical tokens) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/AddParensToTypedLikeExprFix.fs:1 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/AddParensToTypedLikeExprFix.fs:1-38 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveNeverMatchingRuleFix.fs:1-33 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveRedundantNewFix.fs:1-28 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveUnexpectedArgumentsFix.fs:1-36 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveUnusedNamedAsPatFix.fs:1-27 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication · Edited copies of one member (3 members, 19+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 19+ corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveRedundantAttributeParensFix.fs:1 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveRedundantAttributeParensFix.fs:1-19 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveRedundantAttributeSuffixFix.fs:1-20 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/UseWildSelfIdFix.fs:1-23 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×1
  • Edited copy of a member (20 corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveUnnecessaryUpcastFix.fs:1 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveUnnecessaryUpcastFix.fs:1-20 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveUnusedSelfIdVariableFix.fs:1-21 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×1
  • Edited copy of a member (15 corresponding lines) rider-fsharp/src/main/java/com/jetbrains/rider/plugins/fsharp/projectView/FSharpMoveProviderExtension.kt:176 — rider-fsharp/src/main/java/com/jetbrains/rider/plugins/fsharp/projectView/FSharpMoveProviderExtension.kt:176-190 | rider-fsharp/src/main/java/com/jetbrains/rider/plugins/fsharp/projectView/FSharpMoveProviderExtension.kt:192-206 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×1
  • Edited copy of a member (17 corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveConstructorFix.fs:1 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveConstructorFix.fs:1-19 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveInlineFix.fs:1-17 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×1
  • Edited copy of a member (9 corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Comment/FSharpDocCommentElementsItemsProvider.fs:1 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Comment/FSharpDocCommentElementsItemsProvider.fs:1-9 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/LanguageService/FSharpLanguageSpecificCopyPasteBehavior.fs:1-10 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 7+ corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Common/src/ProjectModel/Host/ZoneMarker.fs:1 — ReSharper.FSharp/src/FSharp/FSharp.Common/src/ProjectModel/Host/ZoneMarker.fs:1-7 | ReSharper.FSharp/src/FSharp/FSharp.Common/src/Shim/AssemblyReader/ZoneMarker.fs:1-7 | ReSharper.FSharp/src/FSharp/FSharp.Common/src/Shim/FileSystem/ZoneMarker.fs:1-7 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/LanguageService/ZoneMarker.fs:1-7 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×1
  • Edited copy of a member (8 corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/AI/ZoneMarker.fs:1 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/AI/ZoneMarker.fs:1-8 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/ExternalSources/ZoneMarker.fs:1-9 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 8+ corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Common/src/Checker/ZoneMarker.fs:1 — ReSharper.FSharp/src/FSharp/FSharp.Common/src/Checker/ZoneMarker.fs:1-8 | ReSharper.FSharp/src/FSharp/FSharp.Common/src/ProjectModel/ZoneMarker.fs:1-8 | ReSharper.FSharp/src/FSharp/FSharp.Common/src/Settings/ZoneMarker.fs:1-8 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 8+ corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/PsiFeaturesNamespaceZoneMarker.fs:1 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/PsiFeaturesNamespaceZoneMarker.fs:1-8 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/PsiNamespaceZoneMarker.fs:1-8 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/ZoneMarker.fs:1-8 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/ZoneMarkerServices.fs:1-8 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (20–22 lines × 2) · ×1
  • Duplicated block (20–22 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/StringLiteralsUtil.fs:153 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/StringLiteralsUtil.fs:153-172 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/StringLiteralsUtil.fs:181-202 — 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.
D4 · Code Duplication · Duplicated block (19–20 lines × 2) · ×1
  • Duplicated block (19–20 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Parsing/FSharpImplTreeBuilder.fs:138 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Parsing/FSharpImplTreeBuilder.fs:138-156 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Parsing/FSharpSigTreeBuilder.fs:97-116 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (9–10 lines × 2) · ×1
  • Duplicated block (9–10 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Stages/PatternTypeHintsStage.fs:1 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Stages/PatternTypeHintsStage.fs:1-9 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Stages/PipeChainTypeHintStage.fs:1-10 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (2–7 lines × 10) · ×1
  • Duplicated block (2–7 lines × 10) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/FSharpScriptReferenceCompletionProvider.fs:11 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/FSharpScriptReferenceCompletionProvider.fs:11-12 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateLambdaRule.fs:8-9 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateMatchExprPatternsRule.fs:6-7 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImplementInterfaceMemberRule.fs:6-7 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportModuleMemberRule.fs:4-10 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportTypeElementRule.fs:6-12 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/NameSuggestionRule.fs:6-7 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/OverrideMemberRule.fs:6-7 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ToRecursiveFunctionRule.fs:7-8 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/UnionCaseFieldsRule.fs:6-7 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 10 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 10 times.
D4 · Code Duplication · Duplicated block (5 lines × 10) · ×1
  • Duplicated block (5 lines × 10) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/AddExtensionAttributeFix.fs:1 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/AddExtensionAttributeFix.fs:1-5 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ConvertTupleToArrayOrListElementsFix.fs:1-5 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveIndexerDotFix.fs:1-5 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveRedundantAsPatFix.fs:1-5 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveRedundantQualifierFix.fs:1-5 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveYieldFix.fs:1-5 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ReplaceLambdaWithBuiltinFunctionFix.fs:1-5 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/SimplifyLambdaFix.fs:1-5 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ToAbstractFix.fs:1-5 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ToObjectExpressionFix.fs:1-5 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 10 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (5 lines × 5) · ×1
  • Duplicated block (5 lines × 5) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/AddParensToTypedLikeExprFix.fs:1 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/AddParensToTypedLikeExprFix.fs:1-5 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveNeverMatchingRuleFix.fs:1-5 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveRedundantNewFix.fs:1-5 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveUnexpectedArgumentsFix.fs:1-5 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveUnusedNamedAsPatFix.fs:1-5 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 5 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (4–5 lines × 3) · ×1
  • Duplicated block (4–5 lines × 3) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportModuleMemberRule.fs:18 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportModuleMemberRule.fs:18-21 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportStaticMemberRule.fs:17-21 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/RecordFieldRule.fs:15-19 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×1
  • Duplicated block (8 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/ZoneMarker.fs:1 — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/ZoneMarker.fs:1-8 | ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/ZoneMarker.fs:1-8 — before extracting anything, compare `ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/ZoneMarker.fs` and `ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/ZoneMarker.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
SC1 · Supply-chain hygiene · NuGet dependencies are not locked · ×1
  • NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
Minor — 25 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×8
  • Orphaned file ReSharper.FSharp/src/FSharp/FSharp.Psi/src/Parsing/FSharpPreprocessedLexer.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/FSharpStringLexer.fs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Injected/FSharpRegexNodeProvider.fs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ReSharper.FSharp/src/FSharp/FSharp.Psi/src/Parsing/FSharpPreprocessor.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/Intentions/UseNamedAccessAction.fs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/UpdateParameterNameInSignatureFix.fs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ReplaceWithTripleQuotedInterpolatedStringFix.fs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Injected/FSharpRegexProviders.fs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
X10 · Duplicated predicate · Duplicated predicate · ×4
  • Duplicated predicate ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportModuleMemberRule.fs:72 — `FSharpSymbolReference && context.BasicContext.Solution.GetComponent<IFcsAssemblyReaderShim>().IsEnabled` appears character-identically in 2 files — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportModuleMemberRule.fs, ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportTypeElementRule.fs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportModuleMemberRule.fs:69 — `context.EnableImportCompletion && not context.IsQualified && context.ReparsedContext.Reference` appears character-identically in 2 files — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportModuleMemberRule.fs, ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportTypeElementRule.fs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/FilterFcsItemsRules.fs:52 — `context.IsBasicOrSmartCompletion && not context.IsQualified` appears character-identically in 4 files — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/FilterFcsItemsRules.fs, ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateLambdaRule.fs, ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/NamedArgumentsRule.fs, ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ToRecursiveFunctionRule.fs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/FcsLookupItemsProvider.fs:99 — `tokenBeforeType.IsComment || FSharpTokenType.Strings[tokenBeforeType] || tokenBeforeType.IsConstantLiteral` appears character-identically in 2 files — ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/FcsLookupItemsProvider.fs, ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/FSharpKeywordsRule.fs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
D16 · Bus Factor · Off-boarding risk · ×3
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 28 significant file(s) lose their only recent owner: ReSharper.FSharp/src/FSharp/FSharp.Common/src/Shim/AssemblyReader/ProjectFcsModuleReader.fs, ReSharper.FSharp/src/FSharp/FSharp.Psi/src/Metadata/FSharpMetadataReader.cs, ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/IntroduceVariable.fs, ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/OpensUtil.fs, ReSharper.FSharp/src/FSharp/FSharp.Psi/src/Util/FcsTypeMappingUtil.cs, ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Debugger/FSharpSourceCallableExpressionsProvider.fs, ReSharper.FSharp/src/FSharp/FSharp.Psi/src/Impl/Cache2/FSharpDeclarationProcessor.cs, ReSharper.FSharp/src/FSharp/FSharp.Common/src/Util/FSharpSymbolUtil.fs (+20 more). Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 5 significant file(s) lose their only recent owner: ReSharper.FSharp/src/FSharp/FSharp.TypeProviders.Protocol/src/Models/ProxyProvidedType.cs, ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/Intentions/DisableWarningActions.fs, ReSharper.FSharp/src/FSharp/FSharp.TypeProviders.Protocol/src/Models/ProxyProvidedTypeWithContext.cs, ReSharper.FSharp/src/FSharp/FSharp.Common/src/Checker/FSharpCheckerExtensions.fs, ReSharper.FSharp/src/FSharp.Fantomas.Host/src/FantomasAssemblyResolver.cs. Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 4 significant file(s) lose their only recent owner: ReSharper.FSharp/src/FSharp/FSharp.Psi/src/Impl/Cache2/GenerativeMembersConverter.cs, ReSharper.FSharp/src/FSharp/FSharp.Psi/src/Impl/Cache2/FSharpGenerativeProvidedNestedClass.cs, ReSharper.FSharp/src/FSharp/FSharp.Psi/src/Impl/DeclaredElement/CompilerGenerated/FSharpUnionTagsClass.cs, ReSharper.FSharp/src/FSharp/FSharp.Psi/src/Impl/Cache2/FSharpGenerativeProvidedMember.cs. Pair on, review, or document these before any departure.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 4 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (42 single-owned of 327 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 327 of the 1005 production source files in this repository met that bar). They are anonymized user #4 (2 file(s)), anonymized user #5 (1 file(s)), anonymized user #6 (1 file(s)), anonymized user #7 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/UnionCaseFieldsRule.fs, ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateLambdaRule.fs, ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeStyle/FantomasPage.fs, ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Util/FSharpVisualElementFactory.fs, ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Debugger/FSharpBreakpointVariantsProvider.fs.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found ReSharper.FSharp/src/FSharp.Fantomas.Host/FSharp.Fantomas.Host.csproj:16 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `ReSharper.FSharp/src/FSharp.Fantomas.Host/FSharp.Fantomas.Host.csproj` makes this repository a deployable product (line 16).
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 8 of 331 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 331 of the 1005 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: ReSharper.FSharp/src/FSharp/FSharp.Psi/src/Parsing/FSharpPreprocessedLexer.cs, ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/FSharpStringLexer.fs, ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Injected/FSharpRegexNodeProvider.fs, ReSharper.FSharp/src/FSharp/FSharp.Psi/src/Parsing/FSharpPreprocessor.cs, ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/Intentions/UseNamedAccessAction.fs, ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/UpdateParameterNameInSignatureFix.fs, ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ReplaceWithTripleQuotedInterpolatedStringFix.fs, ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Injected/FSharpRegexProviders.fs. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — 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.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 5/6 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `rider-fsharp/projectTemplates/FSharpConsoleApplicationTemplate`.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:6 — No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation ReSharper.FSharp/Directory.Build.props:17 — `ReSharper.FSharp/Directory.Build.props` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
X5 · Nullable reference types · Nullable reference types not enabled everywhere · ×1
  • Nullable reference types not enabled everywhere — 0/2 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b82c657c041446379c867b745cd933cb/history.json --exit-code 0 --source .0artifacts/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-b82c657c041446379c867b745cd933cb/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude rider-fsharp/src/test/testData/solutions/AsyncProgram/obj --exclude rider-fsharp/src/test/testData/solutions/CeSteppingTests/obj --exclude rider-fsharp/src/test/testData/solutions/ConsoleAppTwoTargetFrameworks/obj --exclude rider-fsharp/src/test/testData/solutions/CoreConsoleApp/obj --exclude rider-fsharp/src/test/testData/solutions/CoreTypeProviderLibrary/TypeProviderLibrary/obj --exclude rider-fsharp/src/test/testData/solutions/CsvTypeProvider/TypeProviderLibrary/obj --exclude rider-fsharp/src/test/testData/solutions/EmptyFolders/ClassLibrary1/obj --exclude rider-fsharp/src/test/testData/solutions/FSharpProjectTree/ClassLibrary1/obj --exclude rider-fsharp/src/test/testData/solutions/FableApp/obj --exclude rider-fsharp/src/test/testData/solutions/FileNesting/ClassLibrary1/obj --exclude rider-fsharp/src/test/testData/solutions/FolderWithEmptySub/ClassLibrary1/obj --exclude rider-fsharp/src/test/testData/solutions/FormatCodeApp/FormatCodeApp/obj --exclude rider-fsharp/src/test/testData/solutions/FsprojWithTwoFiles/ClassLibrary1/obj --exclude rider-fsharp/src/test/testData/solutions/InterleavedFolder/ClassLibrary1/obj --exclude rider-fsharp/src/test/testData/solutions/LegacyTypeProviderLibrary/TypeProviderLibrary/obj --exclude rider-fsharp/src/test/testData/solutions/LinkBase/ClassLibrary1/obj --exclude rider-fsharp/src/test/testData/solutions/MoveProviderSolution1/obj --exclude rider-fsharp/src/test/testData/solutions/MoveProviderSolution2/obj --exclude rider-fsharp/src/test/testData/solutions/MoveProviderSolution3/obj --exclude rider-fsharp/src/test/testData/solutions/ProjectReferencesCSharp/FSharpProject/obj --exclude rider-fsharp/src/test/testData/solutions/ProjectReferencesCSharp2/CSharpProject/obj --exclude rider-fsharp/src/test/testData/solutions/ProjectReferencesCSharp2/FSharpProject/obj --exclude rider-fsharp/src/test/testData/solutions/ProjectReferencesCSharp3/CSharpProject/obj --exclude rider-fsharp/src/test/testData/solutions/ProjectReferencesCSharp3/FSharpProject/obj --exclude rider-fsharp/src/test/testData/solutions/ProjectReferencesFSharp/ReferenceFrom/obj --exclude rider-fsharp/src/test/testData/solutions/ProjectReferencesFSharp/ReferenceTo/obj --exclude rider-fsharp/src/test/testData/solutions/ReferencesOrder/obj --exclude rider-fsharp/src/test/testData/solutions/ReturnValueTest/obj --exclude rider-fsharp/src/test/testData/solutions/SmartStepIntoTest/obj --exclude rider-fsharp/src/test/testData/solutions/SolutionWithDuplicateTargets/SolutionWithDuplicateTargets/obj --exclude rider-fsharp/src/test/testData/solutions/SolutionWithExplicitItemBetweenSources/App/obj --exclude rider-fsharp/src/test/testData/solutions/SolutionWithGlobInFolderItem/Tests/obj --exclude rider-fsharp/src/test/testData/solutions/SolutionWithImportedXamlItems/App/obj --exclude rider-fsharp/src/test/testData/solutions/SplitNested/ClassLibrary1/obj --exclude rider-fsharp/src/test/testData/solutions/SplitNestedTwoFolders/ClassLibrary1/obj --exclude rider-fsharp/src/test/testData/solutions/SplitNestedWithFile/ClassLibrary1/obj --exclude rider-fsharp/src/test/testData/solutions/SteppingTests/obj --exclude rider-fsharp/src/test/testData/solutions/SwaggerProviderCSharp/SwaggerProviderLibrary/obj --exclude rider-fsharp/src/test/testData/solutions/TypeProviderLibrary/GenerativeTypeLibrary/obj --exclude rider-fsharp/src/test/testData/solutions/TypeProviderLibrary/GenerativeTypeProvider/obj --exclude rider-fsharp/src/test/testData/solutions/TypeProviderLibrary/TypeProviderLibrary/obj --exclude rider-fsharp/src/test/testData/solutions/TypeProviderLibrary/TypeProviderLibrary2/obj .9artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnuget—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; nuget packages.config: osv-scanner exited 127 with no findings — dependency CVEs were not measured0—
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 99 file(s) — `ReSharper.FSharp/src/FSharp.Debugger/src/FSharpAsyncStepper.cs`, `ReSharper.FSharp/src/FSharp.Debugger/src/FSharpSequencePointInvokedMethodsProvider.cs`, `ReSharper.FSharp/src/FSharp.Debugger/src/FSharpUnitReturnValueFilter.cs`, `ReSharper.FSharp/src/FSharp/FSharp.ProjectModelBase/src/FSharpAsyncUtil.cs`, `ReSharper.FSharp/src/FSharp/FSharp.ProjectModelBase/src/FSharpZones.cs`, … (+94 more) — 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 Policydisclosure—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 Confinementruntime-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 Confinementruntime-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 Enforcementruntime-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 Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-131c1a97cc8f44b8a8edf8f1178c273c0artifacts/raw/osv-scanner.json

Run 01a1d4b5-fe69-7f35-a5ea-6c7abfd6e0f9 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md