Executive summary
dotnet/BenchmarkDotNet falls short of our standard for a preview release because we found no encryption of stored data, no key vault and no enforced HTTPS, and it has passwords or keys in the code's history. It scores 50 out of 100 and is rated Adequate, and 93 of its 159 critical findings are security problems.
Security and Compliance, at 33, is the weakest lens and counts most in the score. The best first step is encrypting the sensitive stored data and keeping its keys in a vault, worth about 12 points. Replacing the 11 passwords or keys found in the code's history comes next, worth about 7 points. Raising Security and Compliance to 68 would lift the score to about 65.
Sixty-four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Twelve passwords or keys are open to anyone who can read the repository, and eighteen errors are caught and ignored, so failures can go unnoticed. Pinning each tool to an exact version, replacing each exposed password or key and handling or logging the ignored errors would close these risks. Limiting each secret to its own step would fix the five secrets exposed to more of the pipeline than needed, and fixing the weaknesses the scanner points to would deal with the five security weaknesses in the code. The 22 sets of compiler warnings switched off in projects need turning back on in the build file.
The product code is 60,623 lines, about €260,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Security and Compliance rose from 33 to 68, the lowest score rated Strong, the score would rise from 50 to about 65.
New since the last survey: 103 findings
- Cognitive Complexity · ProcessExtensions.SetCoreRunEnvironmentVariables (cognitive 16) src/BenchmarkDotNet/Extensions/ProcessExtensions.cs
- Cognitive Complexity · ReflectionExtensions.GetCorrectCSharpTypeName (cognitive 16) src/BenchmarkDotNet/Extensions/ReflectionExtensions.cs
- Code Duplication · Edited copy of a member (74 corresponding lines) src/BenchmarkDotNet.Exporters.Plotting/ScottPlotExporter.cs
- Code Duplication · Edited copy of a member (49 corresponding lines) src/BenchmarkDotNet.Diagnostics.Windows/InliningDiagnoser.cs
- Code Duplication · Edited copy of a member (69 corresponding lines) src/BenchmarkDotNet/Parameters/DeepEqualityComparer.cs
- Code Duplication · Edited copy of a member (38 corresponding lines) REDACTED
- Code Duplication · Edited copy of a member (52 corresponding lines) src/BenchmarkDotNet.Analyzers/Attributes/SetupCleanupAsyncEnumerableAnalyzer.cs
- Code Duplication · Edited copy of a member (45 corresponding lines) src/BenchmarkDotNet.Analyzers/Attributes/BenchmarkCancellationAttributeAnalyzer.cs
- Code Duplication · Edited copy of a member (31 corresponding lines) src/BenchmarkDotNet.Analyzers/Attributes/SetupCleanupAsyncEnumerableAnalyzer.cs
- Code Duplication · Edited copy of a member (26 corresponding lines) src/BenchmarkDotNet.Analyzers/AnalyzerHelper.cs
- Code Duplication · Edited copy of a member (26 corresponding lines) src/BenchmarkDotNet/Helpers/CancelableStreamWriter.cs
- Code Duplication · Edited copy of a member (20 corresponding lines) src/BenchmarkDotNet/Engines/GcStats.cs
- Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) src/BenchmarkDotNet/Extensions/TaskExtensions.cs
- Code Duplication · Edited copy of a member (25 corresponding lines) src/BenchmarkDotNet.Analyzers/AnalyzerHelper.cs
- Code Duplication · Edited copy of a member (6 corresponding lines) src/BenchmarkDotNet/Extensions/TaskExtensions.cs
- Code Duplication · Edited copies of one member (4 members, 16+ corresponding lines) src/BenchmarkDotNet.Analyzers/Attributes/ArgumentsAttributeAnalyzer.cs
- Code Duplication · Edited copy of a member (15 corresponding lines) src/BenchmarkDotNet.Analyzers/Attributes/ParamsAttributeAnalyzer.cs
- Code Duplication · Edited copy of a member (7 corresponding lines) src/BenchmarkDotNet.Diagnostics.dotMemory/DotMemoryDiagnoser.cs
- Code Duplication · Duplicated block (15 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/InProcessEmitRunner.cs
- Code Duplication · Edited copy of a member (9 corresponding lines) samples/BenchmarkDotNet.Samples/IntroDisassembly.cs
- Code Duplication · Edited copy of a member (6 corresponding lines) samples/BenchmarkDotNet.Samples/IntroHardwareCounters.cs
- Churn × Complexity Hotspots · Hotspot: src/BenchmarkDotNet/Disassemblers/ClrMdDisassembler.cs src/BenchmarkDotNet/Disassemblers/ClrMdDisassembler.cs
- Churn × Complexity Hotspots · Hotspot: src/BenchmarkDotNet.Analyzers/Attributes/GeneralParameterAttributesAnalyzer.cs src/BenchmarkDotNet.Analyzers/Attributes/GeneralParameterAttributesAnalyzer.cs
- Churn × Complexity Hotspots · Hotspot: src/BenchmarkDotNet.Analyzers/Attributes/ParamsAttributeAnalyzer.cs src/BenchmarkDotNet.Analyzers/Attributes/ParamsAttributeAnalyzer.cs
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Stateful singletons · Stateful shared instance: EventPipeProfiler src/BenchmarkDotNet/Diagnosers/EventPipeProfiler.cs
- Stateful singletons · Stateful shared instance: ExceptionDiagnoser src/BenchmarkDotNet/Diagnosers/ExceptionDiagnoser.cs
- Stateful singletons · Stateful shared instance: PerfCollectProfiler REDACTED
- Stateful singletons · Stateful shared instance: ThreadingDiagnoser src/BenchmarkDotNet/Diagnosers/ThreadingDiagnoser.cs
- Stateful singletons · Stateful shared instance: ConsoleLogger src/BenchmarkDotNet/Loggers/ConsoleLogger.cs
- Stateful singletons · Process-global static state: DefaultConfig src/BenchmarkDotNet/Configs/DefaultConfig.cs
- Stateful singletons · Process-global static state: HostEnvironmentInfo src/BenchmarkDotNet/Environments/HostEnvironmentInfo.cs
- Stateful singletons · Process-global static state: PathFeatures src/BenchmarkDotNet/Extensions/PathFeatures.cs
- Stateful singletons · Process-global static state: UserInteraction src/BenchmarkDotNet/Running/UserInteraction.cs
Fixed since the last survey: 148 findings
- Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) src/BenchmarkDotNet.Analyzers/Attributes/ArgumentsAttributeAnalyzer.cs
- Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) src/BenchmarkDotNet/Helpers/HashCode.cs
- Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitterBase.cs
- Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/BenchmarkActionImpl.cs
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/BenchmarkDotNet.Analyzers/Attributes/ArgumentsAttributeAnalyzer.cs
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/BenchmarkDotNet.Analyzers/Attributes/SetupCleanupAsyncEnumerableAnalyzer.cs
- Code Duplication · Duplicated block (15 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/InProcessEmitRunner.cs
- Code Duplication · Duplicated block (43–47 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/BenchmarkActionImpl.cs
- Code Duplication · Duplicated block (32 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/BenchmarkActionImpl.cs
- Code Duplication · Duplicated block (30 lines × 2) src/BenchmarkDotNet.Analyzers/Attributes/SetupCleanupAsyncEnumerableAnalyzer.cs
- Code Duplication · Duplicated block (30 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/BenchmarkActionImpl.cs
- Code Duplication · Duplicated block (29 lines × 3) src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/BenchmarkActionImpl.cs
- Code Duplication · Duplicated block (24–27 lines × 9) src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/BenchmarkActionImpl.cs
- Code Duplication · Duplicated block (22–24 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/InProcessEmitRunner.cs
- Code Duplication · Duplicated block (23 lines × 2) src/BenchmarkDotNet.Analyzers/Attributes/BenchmarkCancellationAttributeAnalyzer.cs
- Code Duplication · Duplicated block (21 lines × 4) src/BenchmarkDotNet/Helpers/AwaitHelper.cs
- Code Duplication · Duplicated block (21 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/InProcessEmitExecutor.cs
- Code Duplication · Duplicated block (19–21 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/InProcessEmitRunner.cs
- Code Duplication · Duplicated block (20 lines × 2) src/BenchmarkDotNet.Analyzers/Attributes/ArgumentsAttributeAnalyzer.cs
- Code Duplication · Duplicated block (19 lines × 6) src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/BenchmarkActionImpl.cs
- Code Duplication · Duplicated block (18–19 lines × 2) src/BenchmarkDotNet.Analyzers/Attributes/ArgumentsAttributeAnalyzer.cs
- Code Duplication · Duplicated block (18 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/InProcessEmitExecutor.cs
- Code Duplication · Duplicated block (18 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/InProcessEmitExecutor.cs
- Code Duplication · Duplicated block (16 lines × 2) src/BenchmarkDotNet.Analyzers/Attributes/SetupCleanupAsyncEnumerableAnalyzer.cs
- Code Duplication · Duplicated block (16 lines × 2) src/BenchmarkDotNet.Analyzers/Attributes/SetupCleanupAsyncEnumerableAnalyzer.cs
- Code Duplication · Duplicated block (16 lines × 2) src/BenchmarkDotNet/Diagnosers/ExceptionDiagnoser.cs
- Code Duplication · Duplicated block (15 lines × 2) src/BenchmarkDotNet.Analyzers/General/AsyncBenchmarkAnalyzer.cs
- Code Duplication · Duplicated block (15 lines × 2) src/BenchmarkDotNet/Toolchains/DotNetCli/DotNetCliExecutor.cs
- Code Duplication · Duplicated block (13–15 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/SyncCoreEmitter.cs
- Code Duplication · Duplicated block (15 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/SyncCoreEmitter.cs
- Code Duplication · Duplicated block (14 lines × 6) src/BenchmarkDotNet.Analyzers/Attributes/ArgumentsAttributeAnalyzer.cs
- Code Duplication · Duplicated block (14 lines × 2) src/BenchmarkDotNet/Helpers/DynamicAwaitHelper.cs
- Code Duplication · Duplicated block (14 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/InProcessEmitExecutor.cs
- Code Duplication · Duplicated block (13 lines × 3) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs
- Code Duplication · Duplicated block (13 lines × 2) src/BenchmarkDotNet/Serialization/BdnJsonSerializer.cs
- Code Duplication · Duplicated block (13 lines × 2) src/BenchmarkDotNet/Toolchains/DotNetCli/DotNetCliExecutor.cs
- Code Duplication · Duplicated block (13 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitterBase.cs
- Code Duplication · Duplicated block (9–12 lines × 3) src/BenchmarkDotNet/Helpers/HashCode.cs
- Code Duplication · Duplicated block (12 lines × 3) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs
- Code Duplication · Duplicated block (12 lines × 2) src/BenchmarkDotNet/Configs/IConfig.cs
- Code Duplication · Duplicated block (12 lines × 2) src/BenchmarkDotNet/Engines/EngineActualStage.cs
- Code Duplication · Duplicated block (12 lines × 2) src/BenchmarkDotNet/Toolchains/Mono/RoslynMonoAotToolchain.cs
- Code Duplication · Duplicated block (12 lines × 2) src/BenchmarkDotNet/Validators/ExecutionValidator.cs
- Code Duplication · Duplicated block (11 lines × 3) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs
- Code Duplication · Duplicated block (11 lines × 2) src/BenchmarkDotNet.Analyzers/Attributes/GeneralParameterAttributesAnalyzer.cs
- Code Duplication · Duplicated block (4–11 lines × 3) src/BenchmarkDotNet.Diagnostics.Windows/TailCallDiagnoser.cs
- Code Duplication · Duplicated block (11 lines × 2) src/BenchmarkDotNet/Engines/EnginePilotStage.cs
- Code Duplication · Duplicated block (11 lines × 2) src/BenchmarkDotNet/Toolchains/DotNetCli/DotNetCliExecutor.cs
- Code Duplication · Duplicated block (10–11 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitterBase.cs
- Code Duplication · Duplicated block (11 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/InProcessEmitRunner.cs
- Code Duplication · Duplicated block (10 lines × 4) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncEnumerableCoreEmitter.cs
- Code Duplication · Duplicated block (10 lines × 3) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitterBase.cs
- Code Duplication · Duplicated block (9–10 lines × 3) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncEnumerableCoreEmitter.cs
- Code Duplication · Duplicated block (10 lines × 2) src/BenchmarkDotNet.Analyzers/AnalyzerHelper.cs
- Code Duplication · Duplicated block (10 lines × 2) src/BenchmarkDotNet/Columns/BaselineColumn.cs
- Code Duplication · Duplicated block (9–10 lines × 2) src/BenchmarkDotNet/Toolchains/DotNetCli/DotNetCliCommand.cs
- Code Duplication · Duplicated block (9–10 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs
- Code Duplication · Duplicated block (10 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs
- Code Duplication · Duplicated block (10 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/InProcessEmitExecutor.cs
- Code Duplication · Duplicated block (9 lines × 2) src/BenchmarkDotNet.CodeFixers/AsyncBenchmarkCodeFixProvider.cs
- Code Duplication · Duplicated block (9 lines × 2) src/BenchmarkDotNet/Disassemblers/IntelDisassembler.cs
- Code Duplication · Duplicated block (7–9 lines × 2) src/BenchmarkDotNet/Loggers/ConsoleLogger.cs
- Code Duplication · Duplicated block (8 lines × 2) src/BenchmarkDotNet/Engines/EngineActualStage.cs
- Code Duplication · Duplicated block (8 lines × 2) src/BenchmarkDotNet/Reports/SummaryTableExtensions.cs
- Code Duplication · Duplicated block (8 lines × 2) src/BenchmarkDotNet/Reports/SummaryTableExtensions.cs
- Code Duplication · Duplicated block (8 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitterBase.cs
- Code Duplication · Duplicated block (4–8 lines × 3) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitterBase.cs
- Code Duplication · Duplicated block (8 lines × 2) src/BenchmarkDotNet/Validators/BenchmarkCancellationValidator.cs
- Code Duplication · Duplicated block (7 lines × 4) src/BenchmarkDotNet/Helpers/HashCode.cs
- Code Duplication · Duplicated block (7 lines × 3) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs
- Code Duplication · Duplicated block (7 lines × 2) src/BenchmarkDotNet.Analyzers/General/BenchmarkClassAnalyzer.cs
- Code Duplication · Duplicated block (7 lines × 2) src/BenchmarkDotNet.Diagnostics.Windows/InliningDiagnoser.cs
- Code Duplication · Duplicated block (7 lines × 2) src/BenchmarkDotNet/Characteristics/CompositeResolver.cs
- Code Duplication · Duplicated block (7 lines × 2) src/BenchmarkDotNet/Environments/Runtimes/ClrRuntime.cs
- Code Duplication · Duplicated block (7 lines × 2) src/BenchmarkDotNet/Running/BenchmarkRunnerDirty.cs
- Code Duplication · Duplicated block (7 lines × 2) src/BenchmarkDotNet/Toolchains/DotNetCli/DotNetCliExecutor.cs
- Code Duplication · Duplicated block (7 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitterBase.cs
- Code Duplication · Duplicated block (7 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/InProcessEmitRunner.cs
- Code Duplication · Duplicated block (6 lines × 4) src/BenchmarkDotNet/Helpers/HashCode.cs
- Code Duplication · Duplicated block (6 lines × 3) src/BenchmarkDotNet/Toolchains/DotNetCli/DotNetCliExecutor.cs
- Code Duplication · Duplicated block (6 lines × 3) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs
- Code Duplication · Duplicated block (6 lines × 2) src/BenchmarkDotNet/Loggers/Broker.cs
- Code Duplication · Duplicated block (6 lines × 2) src/BenchmarkDotNet/Parameters/DeepEqualityComparer.cs
- Code Duplication · Duplicated block (6 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/RunnableEmitter.cs
- Code Duplication · Duplicated block (5 lines × 3) src/BenchmarkDotNet/Disassemblers/IntelDisassembler.cs
- Code Duplication · Duplicated block (5 lines × 2) src/BenchmarkDotNet/Analysers/MinIterationTimeAnalyser.cs
- Code Duplication · Duplicated block (5 lines × 2) src/BenchmarkDotNet/Configs/ImmutableConfig.cs
- Code Duplication · Duplicated block (5 lines × 2) src/BenchmarkDotNet/Configs/ImmutableConfig.cs
- Code Duplication · Duplicated block (5 lines × 2) src/BenchmarkDotNet/Toolchains/DotNetCli/DotNetCliExecutor.cs
- Code Duplication · Duplicated block (5 lines × 2) src/BenchmarkDotNet/Validators/ExecutionValidator.cs
- Code Duplication · Duplicated block (10 lines × 2) src/BenchmarkDotNet/Serialization/BdnSimpleJsonSerializer.cs
- Code Duplication · Duplicated block (7 lines × 2) src/BenchmarkDotNet/Exporters/InstructionPointerExporter.cs
- Code Duplication · Duplicated block (5 lines × 2) src/BenchmarkDotNet/Validators/ExecutionValidator.cs
- Code Duplication · Duplicated block (5 lines × 2) src/BenchmarkDotNet/Toolchains/DotNetCli/MsBuildErrorMapper.cs
- Code Duplication · Duplicated block (5 lines × 2) src/BenchmarkDotNet/Helpers/Reflection.Emit/IlGeneratorCallExtensions.cs
- Code Duplication · Duplicated block (5 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs
- Code Duplication · Duplicated block (9–11 lines × 2) src/BenchmarkDotNet.TestAdapter/VSTestAdapter.cs
- Code Coverage · Coverage not measured — no coverage collector is wired up
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
Rebuild cost: about €260,000 · Estimate
| Cost to rebuild | €86,000 to €440,000, for 1,427 to 4,596 hours of work, about 1.8 person-years for 1 to 4 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 50. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 60,623 lines of product code |
| Comment lines | The estimate prices 53,461 lines. Comment lines count towards the size of 60,623 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Build | 2 Characteristics | 3 Disassemblers | 4 Mathematics | 5 Toolchains.Results | 6 Exporters | 7 Toolchains.Parameters | 8 ConsoleArguments | 9 Toolchains | 10 Running | 11 Validators | 12 Parameters | 13 Order | 14 Jobs | 15 Environments | 16 Extensions | 17 Helpers | 18 Engines | 19 Reports | 20 EventProcessors | 21 Exporters.OpenMetrics | 22 Configs | 23 Columns | 24 Attributes | 25 Diagnosers | 26 Disassemblers.Exporters | 27 Loggers | 28 Analysers | 29 Toolchains.DotNetCli | 30 Toolchains.InProcess | 31 Toolchains.Roslyn | 32 Diagnostics.Windows | 33 Toolchains.CsProj | 34 Toolchains.InProcess.Emit | 35 Toolchains.InProcess.NoEmit | 36 Toolchains.CoreRun | 37 Toolchains.Framework | 38 Toolchains.Mono | 39 Toolchains.NativeAot | 40 Toolchains.Wasm |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Build | ||||||||||||||||||||||||||||||||||||||||
| 2 Characteristics | ||||||||||||||||||||||||||||||||||||||||
| 3 Disassemblers | 3 | 1 | 1 | 3 | 2 | |||||||||||||||||||||||||||||||||||
| 4 Mathematics | 1 | |||||||||||||||||||||||||||||||||||||||
| 5 Toolchains.Results | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 6 Exporters | 3 | 2 | 1 | 9 | 14 | 6 | 9 | |||||||||||||||||||||||||||||||||
| 7 Toolchains.Parameters | 1 | 1 | 2 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 8 ConsoleArguments | 1 | 1 | 1 | 1 | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||
| 9 Toolchains | 4 | 4 | 2 | 6 | 2 | 3 | 5 | 3 | 3 | |||||||||||||||||||||||||||||||
| 10 Running | 3 | 2 | 1 | 2 | 3 | 5 | 1 | 2 | 5 | 4 | 6 | 1 | 12 | 2 | 7 | 9 | ||||||||||||||||||||||||
| 11 Validators | 2 | 10 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 12 Parameters | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 13 Order | 7 | 2 | 2 | 2 | 3 | |||||||||||||||||||||||||||||||||||
| 14 Jobs | 9 | 2 | 1 | 1 | 7 | 6 | ||||||||||||||||||||||||||||||||||
| 15 Environments | 6 | 12 | 12 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 16 Extensions | 1 | 2 | 2 | 2 | 4 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 17 Helpers | 2 | 4 | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||||
| 18 Engines | 4 | 1 | 2 | 1 | 11 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 19 Reports | 1 | 2 | 1 | 4 | 1 | 1 | 5 | 1 | 6 | 1 | ||||||||||||||||||||||||||||||
| 20 EventProcessors | 2 | 5 | 2 | 4 | ||||||||||||||||||||||||||||||||||||
| 21 Exporters.OpenMetrics | 1 | 2 | 2 | 2 | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||
| 22 Configs | 7 | 6 | 7 | 6 | 9 | 6 | 6 | 14 | 15 | 6 | 13 | |||||||||||||||||||||||||||||
| 23 Columns | 2 | 8 | 16 | 46 | 1 | |||||||||||||||||||||||||||||||||||
| 24 Attributes | 1 | 3 | 1 | 3 | 4 | 12 | 2 | 46 | 1 | 3 | ||||||||||||||||||||||||||||||
| 25 Diagnosers | 6 | 2 | 11 | 18 | 22 | 2 | 18 | 30 | 1 | 9 | 2 | 13 | 11 | |||||||||||||||||||||||||||
| 26 Disassemblers.Exporters | 8 | 4 | 4 | 4 | 5 | 5 | ||||||||||||||||||||||||||||||||||
| 27 Loggers | 2 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 28 Analysers | 19 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 Toolchains.DotNetCli | 2 | 5 | 1 | 1 | 8 | 5 | 3 | 3 | 4 | |||||||||||||||||||||||||||||||
| 30 Toolchains.InProcess | 1 | 3 | 3 | 1 | 3 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||
| 31 Toolchains.Roslyn | 1 | 1 | 5 | 3 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 32 Diagnostics.Windows | 4 | 9 | 10 | 1 | 2 | 4 | 11 | 3 | 33 | 6 | 4 | |||||||||||||||||||||||||||||
| 33 Toolchains.CsProj | 1 | 6 | 2 | 1 | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||
| 34 Toolchains.InProcess.Emit | 2 | 2 | 5 | 2 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 35 Toolchains.InProcess.NoEmit | 1 | 2 | 3 | 5 | 4 | 1 | 1 | 7 | 1 | 1 | ||||||||||||||||||||||||||||||
| 36 Toolchains.CoreRun | 1 | 1 | 1 | 6 | 2 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||
| 37 Toolchains.Framework | 1 | 1 | 3 | 1 | 1 | 2 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||
| 38 Toolchains.Mono | 3 | 1 | 4 | 9 | 5 | 2 | 1 | 1 | 1 | 1 | 3 | 2 | ||||||||||||||||||||||||||||
| 39 Toolchains.NativeAot | 1 | 1 | 1 | 2 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 40 Toolchains.Wasm | 2 | 1 | 1 | 1 | 4 | 4 | 1 | 4 | 2 | 3 | 3 | 1 | 2 |
3→10 Disassemblers uses Running part of a loop✕
- Connections
- 3 pairs of types, where a type in Disassemblers uses a type in Running.
- The types involved
BenchmarkDotNet.Disassemblers.DisassemblyAnalyzer→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Disassemblers.MonoDisassembler→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Disassemblers.MonoDisassembler→BenchmarkDotNet.Running.Descriptor
- Direction
- Disassemblers uses Running, so a change to Running can break Disassemblers, while a change to Disassemblers can't break Running.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→14 Disassemblers uses Jobs part of a loop✕
- Connections
- 1 pair of types, where a type in Disassemblers uses a type in Jobs.
- The types involved
BenchmarkDotNet.Disassemblers.MonoDisassembler→BenchmarkDotNet.Jobs.Job
- Direction
- Disassemblers uses Jobs, so a change to Jobs can break Disassemblers, while a change to Disassemblers can't break Jobs.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→19 Disassemblers uses Reports part of a loop✕
- Connections
- 1 pair of types, where a type in Disassemblers uses a type in Reports.
- The types involved
BenchmarkDotNet.Disassemblers.DisassemblyAnalyzer→BenchmarkDotNet.Reports.Summary
- Direction
- Disassemblers uses Reports, so a change to Reports can break Disassemblers, while a change to Disassemblers can't break Reports.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→25 Disassemblers uses Diagnosers part of a loop✕
- Connections
- 3 pairs of types, where a type in Disassemblers uses a type in Diagnosers.
- The types involved
BenchmarkDotNet.Disassemblers.Arm64Disassembler→BenchmarkDotNet.Diagnosers.DisassemblySyntaxBenchmarkDotNet.Disassemblers.ClrMdDisassembler→BenchmarkDotNet.Diagnosers.DisassemblySyntaxBenchmarkDotNet.Disassemblers.IntelDisassembler→BenchmarkDotNet.Diagnosers.DisassemblySyntax
- Direction
- Disassemblers uses Diagnosers, so a change to Diagnosers can break Disassemblers, while a change to Disassemblers can't break Diagnosers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→28 Disassemblers uses Analysers part of a loop✕
- Connections
- 2 pairs of types, where a type in Disassemblers uses a type in Analysers.
- The types involved
BenchmarkDotNet.Disassemblers.DisassemblyAnalyzer→BenchmarkDotNet.Analysers.ConclusionBenchmarkDotNet.Disassemblers.DisassemblyAnalyzer→BenchmarkDotNet.Analysers.IAnalyser
- Direction
- Disassemblers uses Analysers, so a change to Analysers can break Disassemblers, while a change to Disassemblers can't break Analysers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→19 Mathematics uses Reports part of a loop✕
- Connections
- 1 pair of types, where a type in Mathematics uses a type in Reports.
- The types involved
BenchmarkDotNet.Mathematics.MeasurementsStatistics→BenchmarkDotNet.Reports.Measurement
- Direction
- Mathematics uses Reports, so a change to Reports can break Mathematics, while a change to Mathematics can't break Reports.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→9 Toolchains.Results uses Toolchains part of a loop✕
- Connections
- 1 pair of types, where a type in Toolchains.Results uses a type in Toolchains.
- The types involved
BenchmarkDotNet.Toolchains.Results.BuildResult→BenchmarkDotNet.Toolchains.ArtifactsPaths
- Direction
- Toolchains.Results uses Toolchains, so a change to Toolchains can break Toolchains.Results, while a change to Toolchains.Results can't break Toolchains.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→18 Toolchains.Results uses Engines part of a loop✕
- Connections
- 2 pairs of types, where a type in Toolchains.Results uses a type in Engines.
- The types involved
BenchmarkDotNet.Toolchains.Results.ExecuteResult→BenchmarkDotNet.Engines.GcStatsBenchmarkDotNet.Toolchains.Results.ExecuteResult→BenchmarkDotNet.Engines.RunResults
- Direction
- Toolchains.Results uses Engines, so a change to Engines can break Toolchains.Results, while a change to Toolchains.Results can't break Engines.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→19 Toolchains.Results uses Reports part of a loop✕
- Connections
- 1 pair of types, where a type in Toolchains.Results uses a type in Reports.
- The types involved
BenchmarkDotNet.Toolchains.Results.ExecuteResult→BenchmarkDotNet.Reports.Measurement
- Direction
- Toolchains.Results uses Reports, so a change to Reports can break Toolchains.Results, while a change to Toolchains.Results can't break Reports.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→27 Toolchains.Results uses Loggers part of a loop✕
- Connections
- 1 pair of types, where a type in Toolchains.Results uses a type in Loggers.
- The types involved
BenchmarkDotNet.Toolchains.Results.ExecuteResult→BenchmarkDotNet.Loggers.ILogger
- Direction
- Toolchains.Results uses Loggers, so a change to Loggers can break Toolchains.Results, while a change to Toolchains.Results can't break Loggers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→3 Exporters uses Disassemblers✕
- Connections
- 3 pairs of types, where a type in Exporters uses a type in Disassemblers.
- The types involved
BenchmarkDotNet.Exporters.CodeWithCounters→BenchmarkDotNet.Disassemblers.SourceCodeBenchmarkDotNet.Exporters.InstructionPointerExporter→BenchmarkDotNet.Disassemblers.DisassemblyResultBenchmarkDotNet.Exporters.MethodWithCounters→BenchmarkDotNet.Disassemblers.DisassembledMethod
- Direction
- Exporters uses Disassemblers, so a change to Disassemblers can break Exporters, while a change to Exporters can't break Disassemblers.
- Position
- Below the diagonal: Exporters uses a module listed above it, which is the healthy direction.
6→10 Exporters uses Running part of a loop✕
- Connections
- 2 pairs of types, where a type in Exporters uses a type in Running.
- The types involved
BenchmarkDotNet.Exporters.FullNameProvider→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Exporters.InstructionPointerExporter→BenchmarkDotNet.Running.BenchmarkCase
- Direction
- Exporters uses Running, so a change to Running can break Exporters, while a change to Exporters can't break Running.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→12 Exporters uses Parameters part of a loop✕
- Connections
- 1 pair of types, where a type in Exporters uses a type in Parameters.
- The types involved
BenchmarkDotNet.Exporters.FullNameProvider→BenchmarkDotNet.Parameters.ParameterInstances
- Direction
- Exporters uses Parameters, so a change to Parameters can break Exporters, while a change to Exporters can't break Parameters.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→17 Exporters uses Helpers part of a loop✕
- Connections
- 9 pairs of types, where a type in Exporters uses a type in Helpers.
- The types involved
BenchmarkDotNet.Exporters.AsciiDocExporter→BenchmarkDotNet.Helpers.CancelableStreamWriterBenchmarkDotNet.Exporters.BenchmarkReportExporter→BenchmarkDotNet.Helpers.CancelableStreamWriterBenchmarkDotNet.Exporters.ExporterBase→BenchmarkDotNet.Helpers.CancelableStreamWriterBenchmarkDotNet.Exporters.HtmlExporter→BenchmarkDotNet.Helpers.CancelableStreamWriterBenchmarkDotNet.Exporters.InstructionPointerExporter→BenchmarkDotNet.Helpers.CancelableStreamWriterBenchmarkDotNet.Exporters.MarkdownExporter→BenchmarkDotNet.Helpers.CancelableStreamWriterBenchmarkDotNet.Exporters.PerfonarJsonExporter→BenchmarkDotNet.Helpers.CancelableStreamWriterBenchmarkDotNet.Exporters.PerfonarMdExporter→BenchmarkDotNet.Helpers.CancelableStreamWriterBenchmarkDotNet.Exporters.PlainExporter→BenchmarkDotNet.Helpers.CancelableStreamWriter
- Direction
- Exporters uses Helpers, so a change to Helpers can break Exporters, while a change to Exporters can't break Helpers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→19 Exporters uses Reports part of a loop✕
- Connections
- 14 pairs of types, where a type in Exporters uses a type in Reports.
- The types involved
BenchmarkDotNet.Exporters.AsciiDocExporter→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Exporters.BenchmarkReportExporter→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Exporters.CompositeExporter→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Exporters.ExporterBase→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Exporters.HtmlExporter→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Exporters.HtmlExporter→BenchmarkDotNet.Reports.SummaryTableBenchmarkDotNet.Exporters.IExporter→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Exporters.InstructionPointerExporter→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Exporters.MarkdownExporter→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Exporters.MarkdownExporter→BenchmarkDotNet.Reports.SummaryTableBenchmarkDotNet.Exporters.PerfonarJsonExporter→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Exporters.PerfonarMdExporter→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Exporters.PlainExporter→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Exporters.RPlotExporter→BenchmarkDotNet.Reports.Summary
- Direction
- Exporters uses Reports, so a change to Reports can break Exporters, while a change to Exporters can't break Reports.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→25 Exporters uses Diagnosers part of a loop✕
- Connections
- 6 pairs of types, where a type in Exporters uses a type in Diagnosers.
- The types involved
BenchmarkDotNet.Exporters.CodeWithCounters→BenchmarkDotNet.Diagnosers.HardwareCounterBenchmarkDotNet.Exporters.InstructionPointerExporter→BenchmarkDotNet.Diagnosers.DisassemblyDiagnoserBenchmarkDotNet.Exporters.InstructionPointerExporter→BenchmarkDotNet.Diagnosers.HardwareCounterBenchmarkDotNet.Exporters.InstructionPointerExporter→BenchmarkDotNet.Diagnosers.IHardwareCountersDiagnoserBenchmarkDotNet.Exporters.InstructionPointerExporter→BenchmarkDotNet.Diagnosers.PmcStatsBenchmarkDotNet.Exporters.MethodWithCounters→BenchmarkDotNet.Diagnosers.HardwareCounter
- Direction
- Exporters uses Diagnosers, so a change to Diagnosers can break Exporters, while a change to Exporters can't break Diagnosers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→27 Exporters uses Loggers part of a loop✕
- Connections
- 9 pairs of types, where a type in Exporters uses a type in Loggers.
- The types involved
BenchmarkDotNet.Exporters.BenchmarkReportExporter→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Exporters.BenchmarkReportExporter→BenchmarkDotNet.Loggers.StreamOrLoggerWriterBenchmarkDotNet.Exporters.CompositeExporter→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Exporters.ExporterBase→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Exporters.IExporter→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Exporters.InstructionPointerExporter→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Exporters.MarkdownExporter→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Exporters.MarkdownExporter→BenchmarkDotNet.Loggers.StreamOrLoggerWriterBenchmarkDotNet.Exporters.RPlotExporter→BenchmarkDotNet.Loggers.ILogger
- Direction
- Exporters uses Loggers, so a change to Loggers can break Exporters, while a change to Exporters can't break Loggers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→2 Toolchains.Parameters uses Characteristics✕
- Connections
- 1 pair of types, where a type in Toolchains.Parameters uses a type in Characteristics.
- The types involved
BenchmarkDotNet.Toolchains.Parameters.ExecuteParameters→BenchmarkDotNet.Characteristics.IResolver
- Direction
- Toolchains.Parameters uses Characteristics, so a change to Characteristics can break Toolchains.Parameters, while a change to Toolchains.Parameters can't break Characteristics.
- Position
- Below the diagonal: Toolchains.Parameters uses a module listed above it, which is the healthy direction.
7→5 Toolchains.Parameters uses Toolchains.Results✕
- Connections
- 1 pair of types, where a type in Toolchains.Parameters uses a type in Toolchains.Results.
- The types involved
BenchmarkDotNet.Toolchains.Parameters.ExecuteParameters→BenchmarkDotNet.Toolchains.Results.BuildResult
- Direction
- Toolchains.Parameters uses Toolchains.Results, so a change to Toolchains.Results can break Toolchains.Parameters, while a change to Toolchains.Parameters can't break Toolchains.Results.
- Position
- Below the diagonal: Toolchains.Parameters uses a module listed above it, which is the healthy direction.
7→10 Toolchains.Parameters uses Running part of a loop✕
- Connections
- 2 pairs of types, where a type in Toolchains.Parameters uses a type in Running.
- The types involved
BenchmarkDotNet.Toolchains.Parameters.ExecuteParameters→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Toolchains.Parameters.ExecuteParameters→BenchmarkDotNet.Running.BenchmarkId
- Direction
- Toolchains.Parameters uses Running, so a change to Running can break Toolchains.Parameters, while a change to Toolchains.Parameters can't break Running.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→25 Toolchains.Parameters uses Diagnosers part of a loop✕
- Connections
- 3 pairs of types, where a type in Toolchains.Parameters uses a type in Diagnosers.
- The types involved
BenchmarkDotNet.Toolchains.Parameters.ExecuteParameters→BenchmarkDotNet.Diagnosers.CompositeInProcessDiagnoserBenchmarkDotNet.Toolchains.Parameters.ExecuteParameters→BenchmarkDotNet.Diagnosers.IDiagnoserBenchmarkDotNet.Toolchains.Parameters.ExecuteParameters→BenchmarkDotNet.Diagnosers.RunMode
- Direction
- Toolchains.Parameters uses Diagnosers, so a change to Diagnosers can break Toolchains.Parameters, while a change to Toolchains.Parameters can't break Diagnosers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→27 Toolchains.Parameters uses Loggers part of a loop✕
- Connections
- 1 pair of types, where a type in Toolchains.Parameters uses a type in Loggers.
- The types involved
BenchmarkDotNet.Toolchains.Parameters.ExecuteParameters→BenchmarkDotNet.Loggers.ILogger
- Direction
- Toolchains.Parameters uses Loggers, so a change to Loggers can break Toolchains.Parameters, while a change to Toolchains.Parameters can't break Loggers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→6 ConsoleArguments uses Exporters✕
- Connections
- 1 pair of types, where a type in ConsoleArguments uses a type in Exporters.
- The types involved
BenchmarkDotNet.ConsoleArguments.ConfigParser→BenchmarkDotNet.Exporters.IExporter
- Direction
- ConsoleArguments uses Exporters, so a change to Exporters can break ConsoleArguments, while a change to ConsoleArguments can't break Exporters.
- Position
- Below the diagonal: ConsoleArguments uses a module listed above it, which is the healthy direction.
8→10 ConsoleArguments uses Running part of a loop✕
- Connections
- 1 pair of types, where a type in ConsoleArguments uses a type in Running.
- The types involved
BenchmarkDotNet.ConsoleArguments.CorrectionsSuggester→BenchmarkDotNet.Running.BenchmarkRunInfo
- Direction
- ConsoleArguments uses Running, so a change to Running can break ConsoleArguments, while a change to ConsoleArguments can't break Running.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→14 ConsoleArguments uses Jobs part of a loop✕
- Connections
- 1 pair of types, where a type in ConsoleArguments uses a type in Jobs.
- The types involved
BenchmarkDotNet.ConsoleArguments.ConfigParser→BenchmarkDotNet.Jobs.Job
- Direction
- ConsoleArguments uses Jobs, so a change to Jobs can break ConsoleArguments, while a change to ConsoleArguments can't break Jobs.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→15 ConsoleArguments uses Environments part of a loop✕
- Connections
- 1 pair of types, where a type in ConsoleArguments uses a type in Environments.
- The types involved
BenchmarkDotNet.ConsoleArguments.CommandLineOptions→BenchmarkDotNet.Environments.Platform
- Direction
- ConsoleArguments uses Environments, so a change to Environments can break ConsoleArguments, while a change to ConsoleArguments can't break Environments.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→18 ConsoleArguments uses Engines part of a loop✕
- Connections
- 2 pairs of types, where a type in ConsoleArguments uses a type in Engines.
- The types involved
BenchmarkDotNet.ConsoleArguments.CommandLineOptions→BenchmarkDotNet.Engines.JitTieringModeBenchmarkDotNet.ConsoleArguments.CommandLineOptions→BenchmarkDotNet.Engines.RunStrategy
- Direction
- ConsoleArguments uses Engines, so a change to Engines can break ConsoleArguments, while a change to ConsoleArguments can't break Engines.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→22 ConsoleArguments uses Configs part of a loop✕
- Connections
- 2 pairs of types, where a type in ConsoleArguments uses a type in Configs.
- The types involved
BenchmarkDotNet.ConsoleArguments.CommandLineOptions→BenchmarkDotNet.Configs.WakeLockTypeBenchmarkDotNet.ConsoleArguments.ConfigParser→BenchmarkDotNet.Configs.IConfig
- Direction
- ConsoleArguments uses Configs, so a change to Configs can break ConsoleArguments, while a change to ConsoleArguments can't break Configs.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→27 ConsoleArguments uses Loggers part of a loop✕
- Connections
- 2 pairs of types, where a type in ConsoleArguments uses a type in Loggers.
- The types involved
BenchmarkDotNet.ConsoleArguments.ConfigParser→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.ConsoleArguments.LoggerWrapper→BenchmarkDotNet.Loggers.ILogger
- Direction
- ConsoleArguments uses Loggers, so a change to Loggers can break ConsoleArguments, while a change to ConsoleArguments can't break Loggers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→2 Toolchains uses Characteristics✕
- Connections
- 4 pairs of types, where a type in Toolchains uses a type in Characteristics.
- The types involved
BenchmarkDotNet.Toolchains.AppConfigGenerator→BenchmarkDotNet.Characteristics.IResolverBenchmarkDotNet.Toolchains.Executor→BenchmarkDotNet.Characteristics.IResolverBenchmarkDotNet.Toolchains.IToolchain→BenchmarkDotNet.Characteristics.IResolverBenchmarkDotNet.Toolchains.Toolchain→BenchmarkDotNet.Characteristics.IResolver
- Direction
- Toolchains uses Characteristics, so a change to Characteristics can break Toolchains, while a change to Toolchains can't break Characteristics.
- Position
- Below the diagonal: Toolchains uses a module listed above it, which is the healthy direction.
9→5 Toolchains uses Toolchains.Results✕
- Connections
- 4 pairs of types, where a type in Toolchains uses a type in Toolchains.Results.
- The types involved
BenchmarkDotNet.Toolchains.BuilderBase→BenchmarkDotNet.Toolchains.Results.BuildResultBenchmarkDotNet.Toolchains.Executor→BenchmarkDotNet.Toolchains.Results.ExecuteResultBenchmarkDotNet.Toolchains.IBuilder→BenchmarkDotNet.Toolchains.Results.BuildResultBenchmarkDotNet.Toolchains.IExecutor→BenchmarkDotNet.Toolchains.Results.ExecuteResult
- Direction
- Toolchains uses Toolchains.Results, so a change to Toolchains.Results can break Toolchains, while a change to Toolchains can't break Toolchains.Results.
- Position
- Below the diagonal: Toolchains uses a module listed above it, which is the healthy direction.
9→7 Toolchains uses Toolchains.Parameters✕
- Connections
- 2 pairs of types, where a type in Toolchains uses a type in Toolchains.Parameters.
- The types involved
BenchmarkDotNet.Toolchains.Executor→BenchmarkDotNet.Toolchains.Parameters.ExecuteParametersBenchmarkDotNet.Toolchains.IExecutor→BenchmarkDotNet.Toolchains.Parameters.ExecuteParameters
- Direction
- Toolchains uses Toolchains.Parameters, so a change to Toolchains.Parameters can break Toolchains, while a change to Toolchains can't break Toolchains.Parameters.
- Position
- Below the diagonal: Toolchains uses a module listed above it, which is the healthy direction.
9→10 Toolchains uses Running part of a loop✕
- Connections
- 6 pairs of types, where a type in Toolchains uses a type in Running.
- The types involved
BenchmarkDotNet.Toolchains.BuilderBase→BenchmarkDotNet.Running.BuildPartitionBenchmarkDotNet.Toolchains.Executor→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Toolchains.Executor→BenchmarkDotNet.Running.BenchmarkIdBenchmarkDotNet.Toolchains.IBuilder→BenchmarkDotNet.Running.BuildPartitionBenchmarkDotNet.Toolchains.IToolchain→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Toolchains.Toolchain→BenchmarkDotNet.Running.BenchmarkCase
- Direction
- Toolchains uses Running, so a change to Running can break Toolchains, while a change to Toolchains can't break Running.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→11 Toolchains uses Validators part of a loop✕
- Connections
- 2 pairs of types, where a type in Toolchains uses a type in Validators.
- The types involved
BenchmarkDotNet.Toolchains.IToolchain→BenchmarkDotNet.Validators.ValidationErrorBenchmarkDotNet.Toolchains.Toolchain→BenchmarkDotNet.Validators.ValidationError
- Direction
- Toolchains uses Validators, so a change to Validators can break Toolchains, while a change to Toolchains can't break Validators.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→14 Toolchains uses Jobs part of a loop✕
- Connections
- 3 pairs of types, where a type in Toolchains uses a type in Jobs.
- The types involved
BenchmarkDotNet.Toolchains.AppConfigGenerator→BenchmarkDotNet.Jobs.EnvironmentModeBenchmarkDotNet.Toolchains.AppConfigGenerator→BenchmarkDotNet.Jobs.GcModeBenchmarkDotNet.Toolchains.AppConfigGenerator→BenchmarkDotNet.Jobs.Job
- Direction
- Toolchains uses Jobs, so a change to Jobs can break Toolchains, while a change to Toolchains can't break Jobs.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→15 Toolchains uses Environments part of a loop✕
- Connections
- 5 pairs of types, where a type in Toolchains uses a type in Environments.
- The types involved
BenchmarkDotNet.Toolchains.IToolchain→BenchmarkDotNet.Environments.RuntimeBenchmarkDotNet.Toolchains.RuntimeTfmExtensions→BenchmarkDotNet.Environments.ClrRuntimeBenchmarkDotNet.Toolchains.RuntimeTfmExtensions→BenchmarkDotNet.Environments.CoreRuntimeBenchmarkDotNet.Toolchains.RuntimeTfmExtensions→BenchmarkDotNet.Environments.RuntimeBenchmarkDotNet.Toolchains.Toolchain→BenchmarkDotNet.Environments.Runtime
- Direction
- Toolchains uses Environments, so a change to Environments can break Toolchains, while a change to Toolchains can't break Environments.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→25 Toolchains uses Diagnosers part of a loop✕
- Connections
- 3 pairs of types, where a type in Toolchains uses a type in Diagnosers.
- The types involved
BenchmarkDotNet.Toolchains.Executor→BenchmarkDotNet.Diagnosers.CompositeInProcessDiagnoserBenchmarkDotNet.Toolchains.Executor→BenchmarkDotNet.Diagnosers.IDiagnoserBenchmarkDotNet.Toolchains.Executor→BenchmarkDotNet.Diagnosers.RunMode
- Direction
- Toolchains uses Diagnosers, so a change to Diagnosers can break Toolchains, while a change to Toolchains can't break Diagnosers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→27 Toolchains uses Loggers part of a loop✕
- Connections
- 3 pairs of types, where a type in Toolchains uses a type in Loggers.
- The types involved
BenchmarkDotNet.Toolchains.BuilderBase→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Toolchains.Executor→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Toolchains.IBuilder→BenchmarkDotNet.Loggers.ILogger
- Direction
- Toolchains uses Loggers, so a change to Loggers can break Toolchains, while a change to Toolchains can't break Loggers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→2 Running uses Characteristics✕
- Connections
- 3 pairs of types, where a type in Running uses a type in Characteristics.
- The types involved
BenchmarkDotNet.Running.BenchmarkPartitioner→BenchmarkDotNet.Characteristics.IResolverBenchmarkDotNet.Running.BenchmarkRunnerClean→BenchmarkDotNet.Characteristics.IResolverBenchmarkDotNet.Running.BuildPartition→BenchmarkDotNet.Characteristics.IResolver
- Direction
- Running uses Characteristics, so a change to Characteristics can break Running, while a change to Running can't break Characteristics.
- Position
- Below the diagonal: Running uses a module listed above it, which is the healthy direction.
10→5 Running uses Toolchains.Results✕
- Connections
- 2 pairs of types, where a type in Running uses a type in Toolchains.Results.
- The types involved
BenchmarkDotNet.Running.BenchmarkRunnerClean→BenchmarkDotNet.Toolchains.Results.BuildResultBenchmarkDotNet.Running.BenchmarkRunnerClean→BenchmarkDotNet.Toolchains.Results.ExecuteResult
- Direction
- Running uses Toolchains.Results, so a change to Toolchains.Results can break Running, while a change to Running can't break Toolchains.Results.
- Position
- Below the diagonal: Running uses a module listed above it, which is the healthy direction.
10→8 Running uses ConsoleArguments✕
- Connections
- 1 pair of types, where a type in Running uses a type in ConsoleArguments.
- The types involved
BenchmarkDotNet.Running.BenchmarkSwitcher→BenchmarkDotNet.ConsoleArguments.CommandLineOptions
- Direction
- Running uses ConsoleArguments, so a change to ConsoleArguments can break Running, while a change to Running can't break ConsoleArguments.
- Position
- Below the diagonal: Running uses a module listed above it, which is the healthy direction.
10→9 Running uses Toolchains✕
- Connections
- 2 pairs of types, where a type in Running uses a type in Toolchains.
- The types involved
BenchmarkDotNet.Running.BenchmarkCase→BenchmarkDotNet.Toolchains.IToolchainBenchmarkDotNet.Running.BenchmarkRunnerClean→BenchmarkDotNet.Toolchains.IToolchain
- Direction
- Running uses Toolchains, so a change to Toolchains can break Running, while a change to Running can't break Toolchains.
- Position
- Below the diagonal: Running uses a module listed above it, which is the healthy direction.
10→11 Running uses Validators part of a loop✕
- Connections
- 3 pairs of types, where a type in Running uses a type in Validators.
- The types involved
BenchmarkDotNet.Running.BenchmarkConverter→BenchmarkDotNet.Validators.ValidationErrorBenchmarkDotNet.Running.BenchmarkRunInfo→BenchmarkDotNet.Validators.ValidationErrorBenchmarkDotNet.Running.BenchmarkRunnerClean→BenchmarkDotNet.Validators.ValidationError
- Direction
- Running uses Validators, so a change to Validators can break Running, while a change to Running can't break Validators.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→12 Running uses Parameters part of a loop✕
- Connections
- 5 pairs of types, where a type in Running uses a type in Parameters.
- The types involved
BenchmarkDotNet.Running.BenchmarkCase→BenchmarkDotNet.Parameters.ParameterInstancesBenchmarkDotNet.Running.BenchmarkConverter→BenchmarkDotNet.Parameters.ParameterDefinitionBenchmarkDotNet.Running.BenchmarkConverter→BenchmarkDotNet.Parameters.ParameterInstanceBenchmarkDotNet.Running.BenchmarkConverter→BenchmarkDotNet.Parameters.ParameterInstancesBenchmarkDotNet.Running.BenchmarkConverter→BenchmarkDotNet.Parameters.ParameterValue
- Direction
- Running uses Parameters, so a change to Parameters can break Running, while a change to Running can't break Parameters.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→13 Running uses Order part of a loop✕
- Connections
- 1 pair of types, where a type in Running uses a type in Order.
- The types involved
BenchmarkDotNet.Running.DescriptorComparer→BenchmarkDotNet.Order.MethodOrderPolicy
- Direction
- Running uses Order, so a change to Order can break Running, while a change to Running can't break Order.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→14 Running uses Jobs part of a loop✕
- Connections
- 2 pairs of types, where a type in Running uses a type in Jobs.
- The types involved
BenchmarkDotNet.Running.BenchmarkCase→BenchmarkDotNet.Jobs.JobBenchmarkDotNet.Running.BenchmarkRuntimePropertiesComparer→BenchmarkDotNet.Jobs.Argument
- Direction
- Running uses Jobs, so a change to Jobs can break Running, while a change to Running can't break Jobs.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→15 Running uses Environments part of a loop✕
- Connections
- 5 pairs of types, where a type in Running uses a type in Environments.
- The types involved
BenchmarkDotNet.Running.BenchmarkCase→BenchmarkDotNet.Environments.RuntimeBenchmarkDotNet.Running.BuildPartition→BenchmarkDotNet.Environments.JitBenchmarkDotNet.Running.BuildPartition→BenchmarkDotNet.Environments.PlatformBenchmarkDotNet.Running.BuildPartition→BenchmarkDotNet.Environments.RuntimeBenchmarkDotNet.Running.PowerManagementApplier→BenchmarkDotNet.Environments.PowerPlan
- Direction
- Running uses Environments, so a change to Environments can break Running, while a change to Running can't break Environments.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→17 Running uses Helpers part of a loop✕
- Connections
- 4 pairs of types, where a type in Running uses a type in Helpers.
- The types involved
BenchmarkDotNet.Running.BenchmarkRunnerClean→BenchmarkDotNet.Helpers.TaskbarProgressBenchmarkDotNet.Running.ConsoleTitler→BenchmarkDotNet.Helpers.DisposeAtProcessTerminationBenchmarkDotNet.Running.PowerManagementApplier→BenchmarkDotNet.Helpers.DisposeAtProcessTerminationBenchmarkDotNet.Running.WakeLockSentinel→BenchmarkDotNet.Helpers.DisposeAtProcessTermination
- Direction
- Running uses Helpers, so a change to Helpers can break Running, while a change to Running can't break Helpers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→19 Running uses Reports part of a loop✕
- Connections
- 6 pairs of types, where a type in Running uses a type in Reports.
- The types involved
BenchmarkDotNet.Running.BenchmarkConverter→BenchmarkDotNet.Reports.SummaryStyleBenchmarkDotNet.Running.BenchmarkRunner→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Running.BenchmarkRunnerClean→BenchmarkDotNet.Reports.BenchmarkReportBenchmarkDotNet.Running.BenchmarkRunnerClean→BenchmarkDotNet.Reports.MetricBenchmarkDotNet.Running.BenchmarkRunnerClean→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Running.BenchmarkSwitcher→BenchmarkDotNet.Reports.Summary
- Direction
- Running uses Reports, so a change to Reports can break Running, while a change to Running can't break Reports.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→20 Running uses EventProcessors part of a loop✕
- Connections
- 1 pair of types, where a type in Running uses a type in EventProcessors.
- The types involved
BenchmarkDotNet.Running.BenchmarkRunnerClean→BenchmarkDotNet.EventProcessors.EventProcessor
- Direction
- Running uses EventProcessors, so a change to EventProcessors can break Running, while a change to Running can't break EventProcessors.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→22 Running uses Configs part of a loop✕
- Connections
- 12 pairs of types, where a type in Running uses a type in Configs.
- The types involved
BenchmarkDotNet.Running.BenchmarkBuildInfo→BenchmarkDotNet.Configs.ImmutableConfigBenchmarkDotNet.Running.BenchmarkCase→BenchmarkDotNet.Configs.ImmutableConfigBenchmarkDotNet.Running.BenchmarkConverter→BenchmarkDotNet.Configs.IConfigBenchmarkDotNet.Running.BenchmarkConverter→BenchmarkDotNet.Configs.ImmutableConfigBenchmarkDotNet.Running.BenchmarkRunInfo→BenchmarkDotNet.Configs.ImmutableConfigBenchmarkDotNet.Running.BenchmarkRunner→BenchmarkDotNet.Configs.IConfigBenchmarkDotNet.Running.BenchmarkRunnerClean→BenchmarkDotNet.Configs.ImmutableConfigBenchmarkDotNet.Running.BenchmarkSwitcher→BenchmarkDotNet.Configs.IConfigBenchmarkDotNet.Running.BenchmarkSwitcher→BenchmarkDotNet.Configs.ImmutableConfigBenchmarkDotNet.Running.TypeFilter→BenchmarkDotNet.Configs.IConfigBenchmarkDotNet.Running.WakeLock→BenchmarkDotNet.Configs.WakeLockTypeBenchmarkDotNet.Running.WakeLockSentinel→BenchmarkDotNet.Configs.WakeLockType
- Direction
- Running uses Configs, so a change to Configs can break Running, while a change to Running can't break Configs.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→24 Running uses Attributes part of a loop✕
- Connections
- 2 pairs of types, where a type in Running uses a type in Attributes.
- The types involved
BenchmarkDotNet.Running.BenchmarkConverter→BenchmarkDotNet.Attributes.BenchmarkAttributeBenchmarkDotNet.Running.BenchmarkConverter→BenchmarkDotNet.Attributes.TargetedAttribute
- Direction
- Running uses Attributes, so a change to Attributes can break Running, while a change to Running can't break Attributes.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→25 Running uses Diagnosers part of a loop✕
- Connections
- 7 pairs of types, where a type in Running uses a type in Diagnosers.
- The types involved
BenchmarkDotNet.Running.BenchmarkBuildInfo→BenchmarkDotNet.Diagnosers.CompositeInProcessDiagnoserBenchmarkDotNet.Running.BenchmarkId→BenchmarkDotNet.Diagnosers.RunModeBenchmarkDotNet.Running.BenchmarkRunInfo→BenchmarkDotNet.Diagnosers.CompositeInProcessDiagnoserBenchmarkDotNet.Running.BenchmarkRunnerClean→BenchmarkDotNet.Diagnosers.CompositeInProcessDiagnoserBenchmarkDotNet.Running.BenchmarkRunnerClean→BenchmarkDotNet.Diagnosers.IDiagnoserBenchmarkDotNet.Running.BenchmarkRunnerClean→BenchmarkDotNet.Diagnosers.RunModeBenchmarkDotNet.Running.InProcessDiagnoserHandlerExtensions→BenchmarkDotNet.Diagnosers.CompositeInProcessDiagnoser
- Direction
- Running uses Diagnosers, so a change to Diagnosers can break Running, while a change to Running can't break Diagnosers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→27 Running uses Loggers part of a loop✕
- Connections
- 9 pairs of types, where a type in Running uses a type in Loggers.
- The types involved
BenchmarkDotNet.Running.BenchmarkRunnerClean→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Running.BenchmarkRunnerClean→BenchmarkDotNet.Loggers.StreamLoggerBenchmarkDotNet.Running.BenchmarkSwitcher→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Running.IUserInteraction→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Running.PowerManagementApplier→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Running.TypeFilter→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Running.UserInteraction→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Running.WakeLock→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Running.WakeLockSentinel→BenchmarkDotNet.Loggers.ILogger
- Direction
- Running uses Loggers, so a change to Loggers can break Running, while a change to Running can't break Loggers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→2 Validators uses Characteristics✕
- Connections
- 2 pairs of types, where a type in Validators uses a type in Characteristics.
- The types involved
BenchmarkDotNet.Validators.RunModeValidator→BenchmarkDotNet.Characteristics.CharacteristicBenchmarkDotNet.Validators.RunModeValidator→BenchmarkDotNet.Characteristics.CompositeResolver
- Direction
- Validators uses Characteristics, so a change to Characteristics can break Validators, while a change to Validators can't break Characteristics.
- Position
- Below the diagonal: Validators uses a module listed above it, which is the healthy direction.
11→10 Validators uses Running✕
- Connections
- 10 pairs of types, where a type in Validators uses a type in Running.
- The types involved
BenchmarkDotNet.Validators.BenchmarkMethodEqualityComparer→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Validators.CompilationValidator→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Validators.DotNetSdkValidator→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Validators.ExecutionValidator→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Validators.ExecutionValidatorBase→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Validators.ReturnValueValidator→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Validators.RunModeValidator→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Validators.ValidationError→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Validators.ValidationParameters→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Validators.ValidationParameters→BenchmarkDotNet.Running.BenchmarkRunInfo
- Direction
- Validators uses Running, so a change to Running can break Validators, while a change to Validators can't break Running.
- Position
- Below the diagonal: Validators uses a module listed above it, which is the healthy direction.
11→14 Validators uses Jobs part of a loop✕
- Connections
- 2 pairs of types, where a type in Validators uses a type in Jobs.
- The types involved
BenchmarkDotNet.Validators.BenchmarkProcessValidator→BenchmarkDotNet.Jobs.JobBenchmarkDotNet.Validators.RunModeValidator→BenchmarkDotNet.Jobs.RunMode
- Direction
- Validators uses Jobs, so a change to Jobs can break Validators, while a change to Validators can't break Jobs.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→18 Validators uses Engines part of a loop✕
- Connections
- 1 pair of types, where a type in Validators uses a type in Engines.
- The types involved
BenchmarkDotNet.Validators.ValidationErrorReporter→BenchmarkDotNet.Engines.IHost
- Direction
- Validators uses Engines, so a change to Engines can break Validators, while a change to Validators can't break Engines.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→22 Validators uses Configs part of a loop✕
- Connections
- 1 pair of types, where a type in Validators uses a type in Configs.
- The types involved
BenchmarkDotNet.Validators.ValidationParameters→BenchmarkDotNet.Configs.ImmutableConfig
- Direction
- Validators uses Configs, so a change to Configs can break Validators, while a change to Validators can't break Configs.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→11 Parameters uses Validators✕
- Connections
- 1 pair of types, where a type in Parameters uses a type in Validators.
- The types involved
BenchmarkDotNet.Parameters.SmartParamBuilder→BenchmarkDotNet.Validators.ValidationError
- Direction
- Parameters uses Validators, so a change to Validators can break Parameters, while a change to Parameters can't break Validators.
- Position
- Below the diagonal: Parameters uses a module listed above it, which is the healthy direction.
12→19 Parameters uses Reports part of a loop✕
- Connections
- 2 pairs of types, where a type in Parameters uses a type in Reports.
- The types involved
BenchmarkDotNet.Parameters.ParameterInstance→BenchmarkDotNet.Reports.SummaryStyleBenchmarkDotNet.Parameters.SmartParamBuilder→BenchmarkDotNet.Reports.SummaryStyle
- Direction
- Parameters uses Reports, so a change to Reports can break Parameters, while a change to Parameters can't break Reports.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→10 Order uses Running✕
- Connections
- 7 pairs of types, where a type in Order uses a type in Running.
- The types involved
BenchmarkDotNet.Order.BenchmarkComparer→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Order.BenchmarkComparer→BenchmarkDotNet.Running.DescriptorBenchmarkDotNet.Order.BenchmarkParamsEqualityComparer→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Order.DefaultOrderer→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Order.DefaultOrderer→BenchmarkDotNet.Running.DescriptorBenchmarkDotNet.Order.IOrderer→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Order.LogicalGroupComparer→BenchmarkDotNet.Running.BenchmarkCase
- Direction
- Order uses Running, so a change to Running can break Order, while a change to Order can't break Running.
- Position
- Below the diagonal: Order uses a module listed above it, which is the healthy direction.
13→12 Order uses Parameters✕
- Connections
- 2 pairs of types, where a type in Order uses a type in Parameters.
- The types involved
BenchmarkDotNet.Order.BenchmarkComparer→BenchmarkDotNet.Parameters.ParameterInstancesBenchmarkDotNet.Order.DefaultOrderer→BenchmarkDotNet.Parameters.ParameterInstances
- Direction
- Order uses Parameters, so a change to Parameters can break Order, while a change to Order can't break Parameters.
- Position
- Below the diagonal: Order uses a module listed above it, which is the healthy direction.
13→14 Order uses Jobs part of a loop✕
- Connections
- 2 pairs of types, where a type in Order uses a type in Jobs.
- The types involved
BenchmarkDotNet.Order.BenchmarkComparer→BenchmarkDotNet.Jobs.JobBenchmarkDotNet.Order.DefaultOrderer→BenchmarkDotNet.Jobs.Job
- Direction
- Order uses Jobs, so a change to Jobs can break Order, while a change to Order can't break Jobs.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→19 Order uses Reports part of a loop✕
- Connections
- 2 pairs of types, where a type in Order uses a type in Reports.
- The types involved
BenchmarkDotNet.Order.DefaultOrderer→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Order.IOrderer→BenchmarkDotNet.Reports.Summary
- Direction
- Order uses Reports, so a change to Reports can break Order, while a change to Order can't break Reports.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→22 Order uses Configs part of a loop✕
- Connections
- 3 pairs of types, where a type in Order uses a type in Configs.
- The types involved
BenchmarkDotNet.Order.BenchmarkComparer→BenchmarkDotNet.Configs.BenchmarkLogicalGroupRuleBenchmarkDotNet.Order.DefaultOrderer→BenchmarkDotNet.Configs.BenchmarkLogicalGroupRuleBenchmarkDotNet.Order.IOrderer→BenchmarkDotNet.Configs.BenchmarkLogicalGroupRule
- Direction
- Order uses Configs, so a change to Configs can break Order, while a change to Order can't break Configs.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→2 Jobs uses Characteristics✕
- Connections
- 9 pairs of types, where a type in Jobs uses a type in Characteristics.
- The types involved
BenchmarkDotNet.Jobs.AccuracyMode→BenchmarkDotNet.Characteristics.CharacteristicBenchmarkDotNet.Jobs.EnvironmentMode→BenchmarkDotNet.Characteristics.CharacteristicBenchmarkDotNet.Jobs.GcMode→BenchmarkDotNet.Characteristics.CharacteristicBenchmarkDotNet.Jobs.InfrastructureMode→BenchmarkDotNet.Characteristics.CharacteristicBenchmarkDotNet.Jobs.Job→BenchmarkDotNet.Characteristics.CharacteristicBenchmarkDotNet.Jobs.Job→BenchmarkDotNet.Characteristics.CharacteristicObjectBenchmarkDotNet.Jobs.JobMode→BenchmarkDotNet.Characteristics.CharacteristicObjectBenchmarkDotNet.Jobs.MetaMode→BenchmarkDotNet.Characteristics.CharacteristicBenchmarkDotNet.Jobs.RunMode→BenchmarkDotNet.Characteristics.Characteristic
- Direction
- Jobs uses Characteristics, so a change to Characteristics can break Jobs, while a change to Jobs can't break Characteristics.
- Position
- Below the diagonal: Jobs uses a module listed above it, which is the healthy direction.
14→9 Jobs uses Toolchains✕
- Connections
- 2 pairs of types, where a type in Jobs uses a type in Toolchains.
- The types involved
BenchmarkDotNet.Jobs.InfrastructureMode→BenchmarkDotNet.Toolchains.IToolchainBenchmarkDotNet.Jobs.JobExtensions→BenchmarkDotNet.Toolchains.IToolchain
- Direction
- Jobs uses Toolchains, so a change to Toolchains can break Jobs, while a change to Jobs can't break Toolchains.
- Position
- Below the diagonal: Jobs uses a module listed above it, which is the healthy direction.
14→10 Jobs uses Running✕
- Connections
- 1 pair of types, where a type in Jobs uses a type in Running.
- The types involved
BenchmarkDotNet.Jobs.JobExtensions→BenchmarkDotNet.Running.Descriptor
- Direction
- Jobs uses Running, so a change to Running can break Jobs, while a change to Jobs can't break Running.
- Position
- Below the diagonal: Jobs uses a module listed above it, which is the healthy direction.
14→13 Jobs uses Order✕
- Connections
- 1 pair of types, where a type in Jobs uses a type in Order.
- The types involved
BenchmarkDotNet.Jobs.JobComparer→BenchmarkDotNet.Order.JobOrderPolicy
- Direction
- Jobs uses Order, so a change to Order can break Jobs, while a change to Jobs can't break Order.
- Position
- Below the diagonal: Jobs uses a module listed above it, which is the healthy direction.
14→15 Jobs uses Environments part of a loop✕
- Connections
- 7 pairs of types, where a type in Jobs uses a type in Environments.
- The types involved
BenchmarkDotNet.Jobs.EnvironmentMode→BenchmarkDotNet.Environments.JitBenchmarkDotNet.Jobs.EnvironmentMode→BenchmarkDotNet.Environments.PlatformBenchmarkDotNet.Jobs.InfrastructureMode→BenchmarkDotNet.Environments.RuntimeBenchmarkDotNet.Jobs.JobExtensions→BenchmarkDotNet.Environments.JitBenchmarkDotNet.Jobs.JobExtensions→BenchmarkDotNet.Environments.PlatformBenchmarkDotNet.Jobs.JobExtensions→BenchmarkDotNet.Environments.PowerPlanBenchmarkDotNet.Jobs.JobExtensions→BenchmarkDotNet.Environments.Runtime
- Direction
- Jobs uses Environments, so a change to Environments can break Jobs, while a change to Jobs can't break Environments.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→18 Jobs uses Engines part of a loop✕
- Connections
- 6 pairs of types, where a type in Jobs uses a type in Engines.
- The types involved
BenchmarkDotNet.Jobs.InfrastructureMode→BenchmarkDotNet.Engines.IEngineFactoryBenchmarkDotNet.Jobs.JobExtensions→BenchmarkDotNet.Engines.IEngineFactoryBenchmarkDotNet.Jobs.JobExtensions→BenchmarkDotNet.Engines.JitTieringModeBenchmarkDotNet.Jobs.JobExtensions→BenchmarkDotNet.Engines.RunStrategyBenchmarkDotNet.Jobs.RunMode→BenchmarkDotNet.Engines.JitTieringModeBenchmarkDotNet.Jobs.RunMode→BenchmarkDotNet.Engines.RunStrategy
- Direction
- Jobs uses Engines, so a change to Engines can break Jobs, while a change to Jobs can't break Engines.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→2 Environments uses Characteristics✕
- Connections
- 6 pairs of types, where a type in Environments uses a type in Characteristics.
- The types involved
BenchmarkDotNet.Environments.EnvironmentResolver→BenchmarkDotNet.Characteristics.IResolverBenchmarkDotNet.Environments.EnvironmentResolver→BenchmarkDotNet.Characteristics.ResolverBenchmarkDotNet.Environments.GcResolver→BenchmarkDotNet.Characteristics.IResolverBenchmarkDotNet.Environments.GcResolver→BenchmarkDotNet.Characteristics.ResolverBenchmarkDotNet.Environments.InfrastructureResolver→BenchmarkDotNet.Characteristics.IResolverBenchmarkDotNet.Environments.InfrastructureResolver→BenchmarkDotNet.Characteristics.Resolver
- Direction
- Environments uses Characteristics, so a change to Characteristics can break Environments, while a change to Environments can't break Characteristics.
- Position
- Below the diagonal: Environments uses a module listed above it, which is the healthy direction.
15→9 Environments uses Toolchains✕
- Connections
- 12 pairs of types, where a type in Environments uses a type in Toolchains.
- The types involved
BenchmarkDotNet.Environments.ClrRuntime→BenchmarkDotNet.Toolchains.IToolchainBenchmarkDotNet.Environments.CoreRuntime→BenchmarkDotNet.Toolchains.IToolchainBenchmarkDotNet.Environments.CoreWasmRuntime→BenchmarkDotNet.Toolchains.IToolchainBenchmarkDotNet.Environments.MonoAotRuntime→BenchmarkDotNet.Toolchains.IToolchainBenchmarkDotNet.Environments.MonoCoreRuntime→BenchmarkDotNet.Toolchains.IToolchainBenchmarkDotNet.Environments.MonoRuntime→BenchmarkDotNet.Toolchains.IToolchainBenchmarkDotNet.Environments.MonoWasmAotRuntime→BenchmarkDotNet.Toolchains.IToolchainBenchmarkDotNet.Environments.MonoWasmRuntime→BenchmarkDotNet.Toolchains.IToolchainBenchmarkDotNet.Environments.NativeAotRuntime→BenchmarkDotNet.Toolchains.IToolchainBenchmarkDotNet.Environments.R2RRuntime→BenchmarkDotNet.Toolchains.IToolchainBenchmarkDotNet.Environments.Runtime→BenchmarkDotNet.Toolchains.IToolchainBenchmarkDotNet.Environments.UnknownRuntime→BenchmarkDotNet.Toolchains.IToolchain
- Direction
- Environments uses Toolchains, so a change to Toolchains can break Environments, while a change to Environments can't break Toolchains.
- Position
- Below the diagonal: Environments uses a module listed above it, which is the healthy direction.
15→10 Environments uses Running✕
- Connections
- 12 pairs of types, where a type in Environments uses a type in Running.
- The types involved
BenchmarkDotNet.Environments.ClrRuntime→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Environments.CoreRuntime→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Environments.CoreWasmRuntime→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Environments.MonoAotRuntime→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Environments.MonoCoreRuntime→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Environments.MonoRuntime→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Environments.MonoWasmAotRuntime→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Environments.MonoWasmRuntime→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Environments.NativeAotRuntime→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Environments.R2RRuntime→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Environments.Runtime→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Environments.UnknownRuntime→BenchmarkDotNet.Running.BenchmarkCase
- Direction
- Environments uses Running, so a change to Running can break Environments, while a change to Environments can't break Running.
- Position
- Below the diagonal: Environments uses a module listed above it, which is the healthy direction.
15→11 Environments uses Validators✕
- Connections
- 1 pair of types, where a type in Environments uses a type in Validators.
- The types involved
BenchmarkDotNet.Environments.BenchmarkEnvironmentInfo→BenchmarkDotNet.Validators.ValidationError
- Direction
- Environments uses Validators, so a change to Validators can break Environments, while a change to Environments can't break Validators.
- Position
- Below the diagonal: Environments uses a module listed above it, which is the healthy direction.
15→14 Environments uses Jobs✕
- Connections
- 1 pair of types, where a type in Environments uses a type in Jobs.
- The types involved
BenchmarkDotNet.Environments.BenchmarkEnvironmentInfo→BenchmarkDotNet.Jobs.Job
- Direction
- Environments uses Jobs, so a change to Jobs can break Environments, while a change to Environments can't break Jobs.
- Position
- Below the diagonal: Environments uses a module listed above it, which is the healthy direction.
16→2 Extensions uses Characteristics✕
- Connections
- 1 pair of types, where a type in Extensions uses a type in Characteristics.
- The types involved
BenchmarkDotNet.Extensions.ProcessExtensions→BenchmarkDotNet.Characteristics.IResolver
- Direction
- Extensions uses Characteristics, so a change to Characteristics can break Extensions, while a change to Extensions can't break Characteristics.
- Position
- Below the diagonal: Extensions uses a module listed above it, which is the healthy direction.
16→4 Extensions uses Mathematics✕
- Connections
- 2 pairs of types, where a type in Extensions uses a type in Mathematics.
- The types involved
BenchmarkDotNet.Extensions.ReportExtensions→BenchmarkDotNet.Mathematics.StatisticsBenchmarkDotNet.Extensions.StatisticsExtensions→BenchmarkDotNet.Mathematics.Statistics
- Direction
- Extensions uses Mathematics, so a change to Mathematics can break Extensions, while a change to Extensions can't break Mathematics.
- Position
- Below the diagonal: Extensions uses a module listed above it, which is the healthy direction.
16→10 Extensions uses Running✕
- Connections
- 2 pairs of types, where a type in Extensions uses a type in Running.
- The types involved
BenchmarkDotNet.Extensions.BenchmarkCaseExtensions→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Extensions.ProcessExtensions→BenchmarkDotNet.Running.BenchmarkCase
- Direction
- Extensions uses Running, so a change to Running can break Extensions, while a change to Extensions can't break Running.
- Position
- Below the diagonal: Extensions uses a module listed above it, which is the healthy direction.
16→15 Extensions uses Environments✕
- Connections
- 2 pairs of types, where a type in Extensions uses a type in Environments.
- The types involved
BenchmarkDotNet.Extensions.ConfigurationExtensions→BenchmarkDotNet.Environments.JitBenchmarkDotNet.Extensions.ConfigurationExtensions→BenchmarkDotNet.Environments.Platform
- Direction
- Extensions uses Environments, so a change to Environments can break Extensions, while a change to Extensions can't break Environments.
- Position
- Below the diagonal: Extensions uses a module listed above it, which is the healthy direction.
16→19 Extensions uses Reports part of a loop✕
- Connections
- 4 pairs of types, where a type in Extensions uses a type in Reports.
- The types involved
BenchmarkDotNet.Extensions.CommonExtensions→BenchmarkDotNet.Reports.SummaryStyleBenchmarkDotNet.Extensions.ReportExtensions→BenchmarkDotNet.Reports.BenchmarkReportBenchmarkDotNet.Extensions.ReportExtensions→BenchmarkDotNet.Reports.MeasurementBenchmarkDotNet.Extensions.ReportExtensions→BenchmarkDotNet.Reports.Summary
- Direction
- Extensions uses Reports, so a change to Reports can break Extensions, while a change to Extensions can't break Reports.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→23 Extensions uses Columns part of a loop✕
- Connections
- 1 pair of types, where a type in Extensions uses a type in Columns.
- The types involved
BenchmarkDotNet.Extensions.CommonExtensions→BenchmarkDotNet.Columns.IColumn
- Direction
- Extensions uses Columns, so a change to Columns can break Extensions, while a change to Extensions can't break Columns.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→27 Extensions uses Loggers part of a loop✕
- Connections
- 2 pairs of types, where a type in Extensions uses a type in Loggers.
- The types involved
BenchmarkDotNet.Extensions.ProcessExtensions→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Extensions.ThreadExtensions→BenchmarkDotNet.Loggers.ILogger
- Direction
- Extensions uses Loggers, so a change to Loggers can break Extensions, while a change to Extensions can't break Loggers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→10 Helpers uses Running✕
- Connections
- 2 pairs of types, where a type in Helpers uses a type in Running.
- The types involved
BenchmarkDotNet.Helpers.TitleHelper→BenchmarkDotNet.Running.BenchmarkRunInfoBenchmarkDotNet.Helpers.UniqueIdGenerator→BenchmarkDotNet.Running.BenchmarkCase
- Direction
- Helpers uses Running, so a change to Running can break Helpers, while a change to Helpers can't break Running.
- Position
- Below the diagonal: Helpers uses a module listed above it, which is the healthy direction.
17→16 Helpers uses Extensions✕
- Connections
- 4 pairs of types, where a type in Helpers uses a type in Extensions.
- The types involved
BenchmarkDotNet.Helpers.DynamicAwaitHelper→BenchmarkDotNet.Extensions.AsyncEnumerableInfoBenchmarkDotNet.Helpers.DynamicAwaitHelper→BenchmarkDotNet.Extensions.AwaitableInfoBenchmarkDotNet.Helpers.DynamicAwaitable→BenchmarkDotNet.Extensions.AwaitableInfoBenchmarkDotNet.Helpers.DynamicAwaiter→BenchmarkDotNet.Extensions.AwaitableInfo
- Direction
- Helpers uses Extensions, so a change to Extensions can break Helpers, while a change to Helpers can't break Extensions.
- Position
- Below the diagonal: Helpers uses a module listed above it, which is the healthy direction.
17→18 Helpers uses Engines part of a loop✕
- Connections
- 1 pair of types, where a type in Helpers uses a type in Engines.
- The types involved
BenchmarkDotNet.Helpers.IpcHelper→BenchmarkDotNet.Engines.IHost
- Direction
- Helpers uses Engines, so a change to Engines can break Helpers, while a change to Helpers can't break Engines.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→25 Helpers uses Diagnosers part of a loop✕
- Connections
- 1 pair of types, where a type in Helpers uses a type in Diagnosers.
- The types involved
BenchmarkDotNet.Helpers.ArtifactFileNameHelper→BenchmarkDotNet.Diagnosers.DiagnoserActionParameters
- Direction
- Helpers uses Diagnosers, so a change to Diagnosers can break Helpers, while a change to Helpers can't break Diagnosers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→27 Helpers uses Loggers part of a loop✕
- Connections
- 4 pairs of types, where a type in Helpers uses a type in Loggers.
- The types involved
BenchmarkDotNet.Helpers.CtrlCCanceler→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Helpers.ProcessCleanupHelper→BenchmarkDotNet.Loggers.AsyncProcessOutputReaderBenchmarkDotNet.Helpers.ProcessCleanupHelper→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Helpers.ProcessHelper→BenchmarkDotNet.Loggers.ILogger
- Direction
- Helpers uses Loggers, so a change to Loggers can break Helpers, while a change to Helpers can't break Loggers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→2 Engines uses Characteristics✕
- Connections
- 4 pairs of types, where a type in Engines uses a type in Characteristics.
- The types involved
BenchmarkDotNet.Engines.Engine→BenchmarkDotNet.Characteristics.IResolverBenchmarkDotNet.Engines.EngineParameters→BenchmarkDotNet.Characteristics.IResolverBenchmarkDotNet.Engines.EngineResolver→BenchmarkDotNet.Characteristics.IResolverBenchmarkDotNet.Engines.EngineResolver→BenchmarkDotNet.Characteristics.Resolver
- Direction
- Engines uses Characteristics, so a change to Characteristics can break Engines, while a change to Engines can't break Characteristics.
- Position
- Below the diagonal: Engines uses a module listed above it, which is the healthy direction.
18→10 Engines uses Running✕
- Connections
- 1 pair of types, where a type in Engines uses a type in Running.
- The types involved
BenchmarkDotNet.Engines.GcStats→BenchmarkDotNet.Running.BenchmarkCase
- Direction
- Engines uses Running, so a change to Running can break Engines, while a change to Engines can't break Running.
- Position
- Below the diagonal: Engines uses a module listed above it, which is the healthy direction.
18→14 Engines uses Jobs✕
- Connections
- 2 pairs of types, where a type in Engines uses a type in Jobs.
- The types involved
BenchmarkDotNet.Engines.Engine→BenchmarkDotNet.Jobs.JobBenchmarkDotNet.Engines.EngineParameters→BenchmarkDotNet.Jobs.Job
- Direction
- Engines uses Jobs, so a change to Jobs can break Engines, while a change to Engines can't break Jobs.
- Position
- Below the diagonal: Engines uses a module listed above it, which is the healthy direction.
18→17 Engines uses Helpers✕
- Connections
- 1 pair of types, where a type in Engines uses a type in Helpers.
- The types involved
BenchmarkDotNet.Engines.TcpConnection→BenchmarkDotNet.Helpers.CancelableStreamReader
- Direction
- Engines uses Helpers, so a change to Helpers can break Engines, while a change to Engines can't break Helpers.
- Position
- Below the diagonal: Engines uses a module listed above it, which is the healthy direction.
18→19 Engines uses Reports part of a loop✕
- Connections
- 11 pairs of types, where a type in Engines uses a type in Reports.
- The types involved
BenchmarkDotNet.Engines.EngineActualStageAuto→BenchmarkDotNet.Reports.MeasurementBenchmarkDotNet.Engines.EngineActualStageSpecific→BenchmarkDotNet.Reports.MeasurementBenchmarkDotNet.Engines.EngineJitStage→BenchmarkDotNet.Reports.MeasurementBenchmarkDotNet.Engines.EnginePilotStage→BenchmarkDotNet.Reports.MeasurementBenchmarkDotNet.Engines.EnginePilotStageAuto→BenchmarkDotNet.Reports.MeasurementBenchmarkDotNet.Engines.EnginePilotStageInitial→BenchmarkDotNet.Reports.MeasurementBenchmarkDotNet.Engines.EnginePilotStageSpecific→BenchmarkDotNet.Reports.MeasurementBenchmarkDotNet.Engines.EngineStage→BenchmarkDotNet.Reports.MeasurementBenchmarkDotNet.Engines.EngineWarmupStageAuto→BenchmarkDotNet.Reports.MeasurementBenchmarkDotNet.Engines.EngineWarmupStageSpecific→BenchmarkDotNet.Reports.MeasurementBenchmarkDotNet.Engines.RunResults→BenchmarkDotNet.Reports.Measurement
- Direction
- Engines uses Reports, so a change to Reports can break Engines, while a change to Engines can't break Reports.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→25 Engines uses Diagnosers part of a loop✕
- Connections
- 1 pair of types, where a type in Engines uses a type in Diagnosers.
- The types involved
BenchmarkDotNet.Engines.EngineParameters→BenchmarkDotNet.Diagnosers.CompositeInProcessDiagnoserHandler
- Direction
- Engines uses Diagnosers, so a change to Diagnosers can break Engines, while a change to Engines can't break Diagnosers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→27 Engines uses Loggers part of a loop✕
- Connections
- 2 pairs of types, where a type in Engines uses a type in Loggers.
- The types involved
BenchmarkDotNet.Engines.FileStdOutConnection→BenchmarkDotNet.Loggers.AsyncProcessOutputReaderBenchmarkDotNet.Engines.FileStdOutListener→BenchmarkDotNet.Loggers.AsyncProcessOutputReader
- Direction
- Engines uses Loggers, so a change to Loggers can break Engines, while a change to Engines can't break Loggers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→4 Reports uses Mathematics✕
- Connections
- 1 pair of types, where a type in Reports uses a type in Mathematics.
- The types involved
BenchmarkDotNet.Reports.BenchmarkReport→BenchmarkDotNet.Mathematics.Statistics
- Direction
- Reports uses Mathematics, so a change to Mathematics can break Reports, while a change to Reports can't break Mathematics.
- Position
- Below the diagonal: Reports uses a module listed above it, which is the healthy direction.
19→5 Reports uses Toolchains.Results✕
- Connections
- 2 pairs of types, where a type in Reports uses a type in Toolchains.Results.
- The types involved
BenchmarkDotNet.Reports.BenchmarkReport→BenchmarkDotNet.Toolchains.Results.BuildResultBenchmarkDotNet.Reports.BenchmarkReport→BenchmarkDotNet.Toolchains.Results.ExecuteResult
- Direction
- Reports uses Toolchains.Results, so a change to Toolchains.Results can break Reports, while a change to Reports can't break Toolchains.Results.
- Position
- Below the diagonal: Reports uses a module listed above it, which is the healthy direction.
19→6 Reports uses Exporters✕
- Connections
- 1 pair of types, where a type in Reports uses a type in Exporters.
- The types involved
BenchmarkDotNet.Reports.SummaryTableExtensions→BenchmarkDotNet.Exporters.MarkdownHighlightStrategy
- Direction
- Reports uses Exporters, so a change to Exporters can break Reports, while a change to Reports can't break Exporters.
- Position
- Below the diagonal: Reports uses a module listed above it, which is the healthy direction.
19→10 Reports uses Running✕
- Connections
- 4 pairs of types, where a type in Reports uses a type in Running.
- The types involved
BenchmarkDotNet.Reports.BaseliningStrategy→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Reports.BenchmarkReport→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Reports.Summary→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Reports.SummaryExtensions→BenchmarkDotNet.Running.BenchmarkCase
- Direction
- Reports uses Running, so a change to Running can break Reports, while a change to Reports can't break Running.
- Position
- Below the diagonal: Reports uses a module listed above it, which is the healthy direction.
19→11 Reports uses Validators✕
- Connections
- 1 pair of types, where a type in Reports uses a type in Validators.
- The types involved
BenchmarkDotNet.Reports.Summary→BenchmarkDotNet.Validators.ValidationError
- Direction
- Reports uses Validators, so a change to Validators can break Reports, while a change to Reports can't break Validators.
- Position
- Below the diagonal: Reports uses a module listed above it, which is the healthy direction.
19→13 Reports uses Order✕
- Connections
- 1 pair of types, where a type in Reports uses a type in Order.
- The types involved
BenchmarkDotNet.Reports.Summary→BenchmarkDotNet.Order.IOrderer
- Direction
- Reports uses Order, so a change to Order can break Reports, while a change to Reports can't break Order.
- Position
- Below the diagonal: Reports uses a module listed above it, which is the healthy direction.
19→18 Reports uses Engines✕
- Connections
- 5 pairs of types, where a type in Reports uses a type in Engines.
- The types involved
BenchmarkDotNet.Reports.BenchmarkReport→BenchmarkDotNet.Engines.GcStatsBenchmarkDotNet.Reports.Measurement→BenchmarkDotNet.Engines.IterationModeBenchmarkDotNet.Reports.Measurement→BenchmarkDotNet.Engines.IterationStageBenchmarkDotNet.Reports.MeasurementExtensions→BenchmarkDotNet.Engines.IterationModeBenchmarkDotNet.Reports.MeasurementExtensions→BenchmarkDotNet.Engines.IterationStage
- Direction
- Reports uses Engines, so a change to Engines can break Reports, while a change to Reports can't break Engines.
- Position
- Below the diagonal: Reports uses a module listed above it, which is the healthy direction.
19→22 Reports uses Configs part of a loop✕
- Connections
- 1 pair of types, where a type in Reports uses a type in Configs.
- The types involved
BenchmarkDotNet.Reports.Summary→BenchmarkDotNet.Configs.ImmutableConfig
- Direction
- Reports uses Configs, so a change to Configs can break Reports, while a change to Reports can't break Configs.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→23 Reports uses Columns part of a loop✕
- Connections
- 6 pairs of types, where a type in Reports uses a type in Columns.
- The types involved
BenchmarkDotNet.Reports.DisplayPrecisionManager→BenchmarkDotNet.Columns.IStatisticColumnBenchmarkDotNet.Reports.IMetricDescriptor→BenchmarkDotNet.Columns.UnitTypeBenchmarkDotNet.Reports.Summary→BenchmarkDotNet.Columns.IColumnHidingRuleBenchmarkDotNet.Reports.SummaryExtensions→BenchmarkDotNet.Columns.IColumnBenchmarkDotNet.Reports.SummaryStyle→BenchmarkDotNet.Columns.RatioStyleBenchmarkDotNet.Reports.SummaryTableColumn→BenchmarkDotNet.Columns.IColumn
- Direction
- Reports uses Columns, so a change to Columns can break Reports, while a change to Reports can't break Columns.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→27 Reports uses Loggers part of a loop✕
- Connections
- 1 pair of types, where a type in Reports uses a type in Loggers.
- The types involved
BenchmarkDotNet.Reports.SummaryTableExtensions→BenchmarkDotNet.Loggers.StreamOrLoggerWriter
- Direction
- Reports uses Loggers, so a change to Loggers can break Reports, while a change to Reports can't break Loggers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→5 EventProcessors uses Toolchains.Results✕
- Connections
- 2 pairs of types, where a type in EventProcessors uses a type in Toolchains.Results.
- The types involved
BenchmarkDotNet.EventProcessors.CompositeEventProcessor→BenchmarkDotNet.Toolchains.Results.BuildResultBenchmarkDotNet.EventProcessors.EventProcessor→BenchmarkDotNet.Toolchains.Results.BuildResult
- Direction
- EventProcessors uses Toolchains.Results, so a change to Toolchains.Results can break EventProcessors, while a change to EventProcessors can't break Toolchains.Results.
- Position
- Below the diagonal: EventProcessors uses a module listed above it, which is the healthy direction.
20→10 EventProcessors uses Running✕
- Connections
- 5 pairs of types, where a type in EventProcessors uses a type in Running.
- The types involved
BenchmarkDotNet.EventProcessors.CompositeEventProcessor→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.EventProcessors.CompositeEventProcessor→BenchmarkDotNet.Running.BenchmarkRunInfoBenchmarkDotNet.EventProcessors.CompositeEventProcessor→BenchmarkDotNet.Running.BuildPartitionBenchmarkDotNet.EventProcessors.EventProcessor→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.EventProcessors.EventProcessor→BenchmarkDotNet.Running.BuildPartition
- Direction
- EventProcessors uses Running, so a change to Running can break EventProcessors, while a change to EventProcessors can't break Running.
- Position
- Below the diagonal: EventProcessors uses a module listed above it, which is the healthy direction.
20→11 EventProcessors uses Validators✕
- Connections
- 2 pairs of types, where a type in EventProcessors uses a type in Validators.
- The types involved
BenchmarkDotNet.EventProcessors.CompositeEventProcessor→BenchmarkDotNet.Validators.ValidationErrorBenchmarkDotNet.EventProcessors.EventProcessor→BenchmarkDotNet.Validators.ValidationError
- Direction
- EventProcessors uses Validators, so a change to Validators can break EventProcessors, while a change to EventProcessors can't break Validators.
- Position
- Below the diagonal: EventProcessors uses a module listed above it, which is the healthy direction.
20→19 EventProcessors uses Reports✕
- Connections
- 4 pairs of types, where a type in EventProcessors uses a type in Reports.
- The types involved
BenchmarkDotNet.EventProcessors.CompositeEventProcessor→BenchmarkDotNet.Reports.BenchmarkReportBenchmarkDotNet.EventProcessors.CompositeEventProcessor→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.EventProcessors.EventProcessor→BenchmarkDotNet.Reports.BenchmarkReportBenchmarkDotNet.EventProcessors.EventProcessor→BenchmarkDotNet.Reports.Summary
- Direction
- EventProcessors uses Reports, so a change to Reports can break EventProcessors, while a change to EventProcessors can't break Reports.
- Position
- Below the diagonal: EventProcessors uses a module listed above it, which is the healthy direction.
21→4 Exporters.OpenMetrics uses Mathematics✕
- Connections
- 1 pair of types, where a type in Exporters.OpenMetrics uses a type in Mathematics.
- The types involved
BenchmarkDotNet.Exporters.OpenMetrics.OpenMetricsExporter→BenchmarkDotNet.Mathematics.Statistics
- Direction
- Exporters.OpenMetrics uses Mathematics, so a change to Mathematics can break Exporters.OpenMetrics, while a change to Exporters.OpenMetrics can't break Mathematics.
- Position
- Below the diagonal: Exporters.OpenMetrics uses a module listed above it, which is the healthy direction.
21→6 Exporters.OpenMetrics uses Exporters✕
- Connections
- 2 pairs of types, where a type in Exporters.OpenMetrics uses a type in Exporters.
- The types involved
BenchmarkDotNet.Exporters.OpenMetrics.OpenMetricsExporter→BenchmarkDotNet.Exporters.ExporterBaseBenchmarkDotNet.Exporters.OpenMetrics.OpenMetricsExporter→BenchmarkDotNet.Exporters.IExporter
- Direction
- Exporters.OpenMetrics uses Exporters, so a change to Exporters can break Exporters.OpenMetrics, while a change to Exporters.OpenMetrics can't break Exporters.
- Position
- Below the diagonal: Exporters.OpenMetrics uses a module listed above it, which is the healthy direction.
21→10 Exporters.OpenMetrics uses Running✕
- Connections
- 2 pairs of types, where a type in Exporters.OpenMetrics uses a type in Running.
- The types involved
BenchmarkDotNet.Exporters.OpenMetrics.OpenMetric→BenchmarkDotNet.Running.DescriptorBenchmarkDotNet.Exporters.OpenMetrics.OpenMetricsExporter→BenchmarkDotNet.Running.Descriptor
- Direction
- Exporters.OpenMetrics uses Running, so a change to Running can break Exporters.OpenMetrics, while a change to Exporters.OpenMetrics can't break Running.
- Position
- Below the diagonal: Exporters.OpenMetrics uses a module listed above it, which is the healthy direction.
21→12 Exporters.OpenMetrics uses Parameters✕
- Connections
- 2 pairs of types, where a type in Exporters.OpenMetrics uses a type in Parameters.
- The types involved
BenchmarkDotNet.Exporters.OpenMetrics.OpenMetric→BenchmarkDotNet.Parameters.ParameterInstancesBenchmarkDotNet.Exporters.OpenMetrics.OpenMetricsExporter→BenchmarkDotNet.Parameters.ParameterInstances
- Direction
- Exporters.OpenMetrics uses Parameters, so a change to Parameters can break Exporters.OpenMetrics, while a change to Exporters.OpenMetrics can't break Parameters.
- Position
- Below the diagonal: Exporters.OpenMetrics uses a module listed above it, which is the healthy direction.
21→17 Exporters.OpenMetrics uses Helpers✕
- Connections
- 1 pair of types, where a type in Exporters.OpenMetrics uses a type in Helpers.
- The types involved
BenchmarkDotNet.Exporters.OpenMetrics.OpenMetricsExporter→BenchmarkDotNet.Helpers.CancelableStreamWriter
- Direction
- Exporters.OpenMetrics uses Helpers, so a change to Helpers can break Exporters.OpenMetrics, while a change to Exporters.OpenMetrics can't break Helpers.
- Position
- Below the diagonal: Exporters.OpenMetrics uses a module listed above it, which is the healthy direction.
21→18 Exporters.OpenMetrics uses Engines✕
- Connections
- 1 pair of types, where a type in Exporters.OpenMetrics uses a type in Engines.
- The types involved
BenchmarkDotNet.Exporters.OpenMetrics.OpenMetricsExporter→BenchmarkDotNet.Engines.GcStats
- Direction
- Exporters.OpenMetrics uses Engines, so a change to Engines can break Exporters.OpenMetrics, while a change to Exporters.OpenMetrics can't break Engines.
- Position
- Below the diagonal: Exporters.OpenMetrics uses a module listed above it, which is the healthy direction.
21→19 Exporters.OpenMetrics uses Reports✕
- Connections
- 3 pairs of types, where a type in Exporters.OpenMetrics uses a type in Reports.
- The types involved
BenchmarkDotNet.Exporters.OpenMetrics.OpenMetric→BenchmarkDotNet.Reports.MetricBenchmarkDotNet.Exporters.OpenMetrics.OpenMetricsExporter→BenchmarkDotNet.Reports.MetricBenchmarkDotNet.Exporters.OpenMetrics.OpenMetricsExporter→BenchmarkDotNet.Reports.Summary
- Direction
- Exporters.OpenMetrics uses Reports, so a change to Reports can break Exporters.OpenMetrics, while a change to Exporters.OpenMetrics can't break Reports.
- Position
- Below the diagonal: Exporters.OpenMetrics uses a module listed above it, which is the healthy direction.
22→6 Configs uses Exporters✕
- Connections
- 7 pairs of types, where a type in Configs uses a type in Exporters.
- The types involved
BenchmarkDotNet.Configs.ConfigExtensions→BenchmarkDotNet.Exporters.IExporterBenchmarkDotNet.Configs.DebugConfig→BenchmarkDotNet.Exporters.IExporterBenchmarkDotNet.Configs.DefaultConfig→BenchmarkDotNet.Exporters.IExporterBenchmarkDotNet.Configs.IConfig→BenchmarkDotNet.Exporters.IExporterBenchmarkDotNet.Configs.ImmutableConfig→BenchmarkDotNet.Exporters.IExporterBenchmarkDotNet.Configs.ImmutableConfigBuilder→BenchmarkDotNet.Exporters.IExporterBenchmarkDotNet.Configs.ManualConfig→BenchmarkDotNet.Exporters.IExporter
- Direction
- Configs uses Exporters, so a change to Exporters can break Configs, while a change to Configs can't break Exporters.
- Position
- Below the diagonal: Configs uses a module listed above it, which is the healthy direction.
22→10 Configs uses Running✕
- Connections
- 6 pairs of types, where a type in Configs uses a type in Running.
- The types involved
BenchmarkDotNet.Configs.DebugConfig→BenchmarkDotNet.Running.ICategoryDiscovererBenchmarkDotNet.Configs.DefaultConfig→BenchmarkDotNet.Running.ICategoryDiscovererBenchmarkDotNet.Configs.IConfig→BenchmarkDotNet.Running.ICategoryDiscovererBenchmarkDotNet.Configs.ImmutableConfig→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Configs.ImmutableConfig→BenchmarkDotNet.Running.ICategoryDiscovererBenchmarkDotNet.Configs.ManualConfig→BenchmarkDotNet.Running.ICategoryDiscoverer
- Direction
- Configs uses Running, so a change to Running can break Configs, while a change to Configs can't break Running.
- Position
- Below the diagonal: Configs uses a module listed above it, which is the healthy direction.
22→11 Configs uses Validators✕
- Connections
- 7 pairs of types, where a type in Configs uses a type in Validators.
- The types involved
BenchmarkDotNet.Configs.ConfigExtensions→BenchmarkDotNet.Validators.IValidatorBenchmarkDotNet.Configs.DebugConfig→BenchmarkDotNet.Validators.IValidatorBenchmarkDotNet.Configs.DefaultConfig→BenchmarkDotNet.Validators.IValidatorBenchmarkDotNet.Configs.IConfig→BenchmarkDotNet.Validators.IValidatorBenchmarkDotNet.Configs.ImmutableConfig→BenchmarkDotNet.Validators.IValidatorBenchmarkDotNet.Configs.ImmutableConfigBuilder→BenchmarkDotNet.Validators.IValidatorBenchmarkDotNet.Configs.ManualConfig→BenchmarkDotNet.Validators.IValidator
- Direction
- Configs uses Validators, so a change to Validators can break Configs, while a change to Configs can't break Validators.
- Position
- Below the diagonal: Configs uses a module listed above it, which is the healthy direction.
22→13 Configs uses Order✕
- Connections
- 6 pairs of types, where a type in Configs uses a type in Order.
- The types involved
BenchmarkDotNet.Configs.ConfigExtensions→BenchmarkDotNet.Order.IOrdererBenchmarkDotNet.Configs.DebugConfig→BenchmarkDotNet.Order.IOrdererBenchmarkDotNet.Configs.DefaultConfig→BenchmarkDotNet.Order.IOrdererBenchmarkDotNet.Configs.IConfig→BenchmarkDotNet.Order.IOrdererBenchmarkDotNet.Configs.ImmutableConfig→BenchmarkDotNet.Order.IOrdererBenchmarkDotNet.Configs.ManualConfig→BenchmarkDotNet.Order.IOrderer
- Direction
- Configs uses Order, so a change to Order can break Configs, while a change to Configs can't break Order.
- Position
- Below the diagonal: Configs uses a module listed above it, which is the healthy direction.
22→14 Configs uses Jobs✕
- Connections
- 9 pairs of types, where a type in Configs uses a type in Jobs.
- The types involved
BenchmarkDotNet.Configs.ConfigExtensions→BenchmarkDotNet.Jobs.JobBenchmarkDotNet.Configs.DebugBuildConfig→BenchmarkDotNet.Jobs.JobBenchmarkDotNet.Configs.DebugConfig→BenchmarkDotNet.Jobs.JobBenchmarkDotNet.Configs.DebugInProcessConfig→BenchmarkDotNet.Jobs.JobBenchmarkDotNet.Configs.DefaultConfig→BenchmarkDotNet.Jobs.JobBenchmarkDotNet.Configs.IConfig→BenchmarkDotNet.Jobs.JobBenchmarkDotNet.Configs.ImmutableConfig→BenchmarkDotNet.Jobs.JobBenchmarkDotNet.Configs.ImmutableConfigBuilder→BenchmarkDotNet.Jobs.JobBenchmarkDotNet.Configs.ManualConfig→BenchmarkDotNet.Jobs.Job
- Direction
- Configs uses Jobs, so a change to Jobs can break Configs, while a change to Configs can't break Jobs.
- Position
- Below the diagonal: Configs uses a module listed above it, which is the healthy direction.
22→19 Configs uses Reports✕
- Connections
- 6 pairs of types, where a type in Configs uses a type in Reports.
- The types involved
BenchmarkDotNet.Configs.ConfigExtensions→BenchmarkDotNet.Reports.SummaryStyleBenchmarkDotNet.Configs.DebugConfig→BenchmarkDotNet.Reports.SummaryStyleBenchmarkDotNet.Configs.DefaultConfig→BenchmarkDotNet.Reports.SummaryStyleBenchmarkDotNet.Configs.IConfig→BenchmarkDotNet.Reports.SummaryStyleBenchmarkDotNet.Configs.ImmutableConfig→BenchmarkDotNet.Reports.SummaryStyleBenchmarkDotNet.Configs.ManualConfig→BenchmarkDotNet.Reports.SummaryStyle
- Direction
- Configs uses Reports, so a change to Reports can break Configs, while a change to Configs can't break Reports.
- Position
- Below the diagonal: Configs uses a module listed above it, which is the healthy direction.
22→20 Configs uses EventProcessors✕
- Connections
- 6 pairs of types, where a type in Configs uses a type in EventProcessors.
- The types involved
BenchmarkDotNet.Configs.ConfigExtensions→BenchmarkDotNet.EventProcessors.EventProcessorBenchmarkDotNet.Configs.DebugConfig→BenchmarkDotNet.EventProcessors.EventProcessorBenchmarkDotNet.Configs.DefaultConfig→BenchmarkDotNet.EventProcessors.EventProcessorBenchmarkDotNet.Configs.IConfig→BenchmarkDotNet.EventProcessors.EventProcessorBenchmarkDotNet.Configs.ImmutableConfig→BenchmarkDotNet.EventProcessors.EventProcessorBenchmarkDotNet.Configs.ManualConfig→BenchmarkDotNet.EventProcessors.EventProcessor
- Direction
- Configs uses EventProcessors, so a change to EventProcessors can break Configs, while a change to Configs can't break EventProcessors.
- Position
- Below the diagonal: Configs uses a module listed above it, which is the healthy direction.
22→23 Configs uses Columns part of a loop✕
- Connections
- 14 pairs of types, where a type in Configs uses a type in Columns.
- The types involved
BenchmarkDotNet.Configs.ConfigExtensions→BenchmarkDotNet.Columns.IColumnBenchmarkDotNet.Configs.ConfigExtensions→BenchmarkDotNet.Columns.IColumnHidingRuleBenchmarkDotNet.Configs.ConfigExtensions→BenchmarkDotNet.Columns.IColumnProviderBenchmarkDotNet.Configs.DebugConfig→BenchmarkDotNet.Columns.IColumnHidingRuleBenchmarkDotNet.Configs.DebugConfig→BenchmarkDotNet.Columns.IColumnProviderBenchmarkDotNet.Configs.DefaultConfig→BenchmarkDotNet.Columns.IColumnHidingRuleBenchmarkDotNet.Configs.DefaultConfig→BenchmarkDotNet.Columns.IColumnProviderBenchmarkDotNet.Configs.IConfig→BenchmarkDotNet.Columns.IColumnHidingRuleBenchmarkDotNet.Configs.IConfig→BenchmarkDotNet.Columns.IColumnProviderBenchmarkDotNet.Configs.ImmutableConfig→BenchmarkDotNet.Columns.IColumnHidingRuleBenchmarkDotNet.Configs.ImmutableConfig→BenchmarkDotNet.Columns.IColumnProviderBenchmarkDotNet.Configs.ManualConfig→BenchmarkDotNet.Columns.IColumnBenchmarkDotNet.Configs.ManualConfig→BenchmarkDotNet.Columns.IColumnHidingRuleBenchmarkDotNet.Configs.ManualConfig→BenchmarkDotNet.Columns.IColumnProvider
- Direction
- Configs uses Columns, so a change to Columns can break Configs, while a change to Configs can't break Columns.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→25 Configs uses Diagnosers part of a loop✕
- Connections
- 15 pairs of types, where a type in Configs uses a type in Diagnosers.
- The types involved
BenchmarkDotNet.Configs.ConfigExtensions→BenchmarkDotNet.Diagnosers.HardwareCounterBenchmarkDotNet.Configs.ConfigExtensions→BenchmarkDotNet.Diagnosers.IDiagnoserBenchmarkDotNet.Configs.DebugConfig→BenchmarkDotNet.Diagnosers.HardwareCounterBenchmarkDotNet.Configs.DebugConfig→BenchmarkDotNet.Diagnosers.IDiagnoserBenchmarkDotNet.Configs.DefaultConfig→BenchmarkDotNet.Diagnosers.HardwareCounterBenchmarkDotNet.Configs.DefaultConfig→BenchmarkDotNet.Diagnosers.IDiagnoserBenchmarkDotNet.Configs.IConfig→BenchmarkDotNet.Diagnosers.HardwareCounterBenchmarkDotNet.Configs.IConfig→BenchmarkDotNet.Diagnosers.IDiagnoserBenchmarkDotNet.Configs.ImmutableConfig→BenchmarkDotNet.Diagnosers.HardwareCounterBenchmarkDotNet.Configs.ImmutableConfig→BenchmarkDotNet.Diagnosers.IDiagnoserBenchmarkDotNet.Configs.ImmutableConfig→BenchmarkDotNet.Diagnosers.RunModeBenchmarkDotNet.Configs.ImmutableConfigBuilder→BenchmarkDotNet.Diagnosers.HardwareCounterBenchmarkDotNet.Configs.ImmutableConfigBuilder→BenchmarkDotNet.Diagnosers.IDiagnoserBenchmarkDotNet.Configs.ManualConfig→BenchmarkDotNet.Diagnosers.HardwareCounterBenchmarkDotNet.Configs.ManualConfig→BenchmarkDotNet.Diagnosers.IDiagnoser
- Direction
- Configs uses Diagnosers, so a change to Diagnosers can break Configs, while a change to Configs can't break Diagnosers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→27 Configs uses Loggers part of a loop✕
- Connections
- 6 pairs of types, where a type in Configs uses a type in Loggers.
- The types involved
BenchmarkDotNet.Configs.ConfigExtensions→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Configs.DebugConfig→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Configs.DefaultConfig→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Configs.IConfig→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Configs.ImmutableConfig→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Configs.ManualConfig→BenchmarkDotNet.Loggers.ILogger
- Direction
- Configs uses Loggers, so a change to Loggers can break Configs, while a change to Configs can't break Loggers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→28 Configs uses Analysers part of a loop✕
- Connections
- 13 pairs of types, where a type in Configs uses a type in Analysers.
- The types involved
BenchmarkDotNet.Configs.ConfigExtensions→BenchmarkDotNet.Analysers.IAnalyserBenchmarkDotNet.Configs.DebugConfig→BenchmarkDotNet.Analysers.ConclusionBenchmarkDotNet.Configs.DebugConfig→BenchmarkDotNet.Analysers.IAnalyserBenchmarkDotNet.Configs.DefaultConfig→BenchmarkDotNet.Analysers.ConclusionBenchmarkDotNet.Configs.DefaultConfig→BenchmarkDotNet.Analysers.IAnalyserBenchmarkDotNet.Configs.IConfig→BenchmarkDotNet.Analysers.ConclusionBenchmarkDotNet.Configs.IConfig→BenchmarkDotNet.Analysers.IAnalyserBenchmarkDotNet.Configs.ImmutableConfig→BenchmarkDotNet.Analysers.ConclusionBenchmarkDotNet.Configs.ImmutableConfig→BenchmarkDotNet.Analysers.IAnalyserBenchmarkDotNet.Configs.ImmutableConfigBuilder→BenchmarkDotNet.Analysers.ConclusionBenchmarkDotNet.Configs.ImmutableConfigBuilder→BenchmarkDotNet.Analysers.IAnalyserBenchmarkDotNet.Configs.ManualConfig→BenchmarkDotNet.Analysers.ConclusionBenchmarkDotNet.Configs.ManualConfig→BenchmarkDotNet.Analysers.IAnalyser
- Direction
- Configs uses Analysers, so a change to Analysers can break Configs, while a change to Configs can't break Analysers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→2 Columns uses Characteristics✕
- Connections
- 2 pairs of types, where a type in Columns uses a type in Characteristics.
- The types involved
BenchmarkDotNet.Columns.JobCharacteristicColumn→BenchmarkDotNet.Characteristics.CharacteristicBenchmarkDotNet.Columns.JobCharacteristicColumn→BenchmarkDotNet.Characteristics.CharacteristicPresenter
- Direction
- Columns uses Characteristics, so a change to Characteristics can break Columns, while a change to Columns can't break Characteristics.
- Position
- Below the diagonal: Columns uses a module listed above it, which is the healthy direction.
23→4 Columns uses Mathematics✕
- Connections
- 8 pairs of types, where a type in Columns uses a type in Mathematics.
- The types involved
BenchmarkDotNet.Columns.BaselineAllocationRatioColumn→BenchmarkDotNet.Mathematics.StatisticsBenchmarkDotNet.Columns.BaselineCustomColumn→BenchmarkDotNet.Mathematics.StatisticsBenchmarkDotNet.Columns.BaselineRatioColumn→BenchmarkDotNet.Mathematics.RatioStatisticsBenchmarkDotNet.Columns.BaselineRatioColumn→BenchmarkDotNet.Mathematics.StatisticsBenchmarkDotNet.Columns.RankColumn→BenchmarkDotNet.Mathematics.NumeralSystemBenchmarkDotNet.Columns.StatisticColumn→BenchmarkDotNet.Mathematics.StatisticsBenchmarkDotNet.Columns.StatisticalTestColumn→BenchmarkDotNet.Mathematics.StatisticsBenchmarkDotNet.Columns.StatisticsColumnProvider→BenchmarkDotNet.Mathematics.Statistics
- Direction
- Columns uses Mathematics, so a change to Mathematics can break Columns, while a change to Columns can't break Mathematics.
- Position
- Below the diagonal: Columns uses a module listed above it, which is the healthy direction.
23→10 Columns uses Running✕
- Connections
- 16 pairs of types, where a type in Columns uses a type in Running.
- The types involved
BenchmarkDotNet.Columns.BaselineAllocationRatioColumn→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Columns.BaselineColumn→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Columns.BaselineCustomColumn→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Columns.BaselineRatioColumn→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Columns.CategoriesColumn→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Columns.IColumn→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Columns.JobCharacteristicColumn→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Columns.LogicalGroupColumn→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Columns.MetricColumn→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Columns.ParamColumn→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Columns.RankColumn→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Columns.SettingsColumn→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Columns.StatisticColumn→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Columns.StatisticalTestColumn→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Columns.TagColumn→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Columns.TargetMethodColumn→BenchmarkDotNet.Running.BenchmarkCase
- Direction
- Columns uses Running, so a change to Running can break Columns, while a change to Columns can't break Running.
- Position
- Below the diagonal: Columns uses a module listed above it, which is the healthy direction.
23→19 Columns uses Reports✕
- Connections
- 46 pairs of types, where a type in Columns uses a type in Reports. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
BenchmarkDotNet.Columns.BaselineAllocationRatioColumn→BenchmarkDotNet.Reports.MetricBenchmarkDotNet.Columns.BaselineAllocationRatioColumn→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Columns.BaselineColumn→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Columns.BaselineColumn→BenchmarkDotNet.Reports.SummaryStyleBenchmarkDotNet.Columns.BaselineCustomColumn→BenchmarkDotNet.Reports.MetricBenchmarkDotNet.Columns.BaselineCustomColumn→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Columns.BaselineCustomColumn→BenchmarkDotNet.Reports.SummaryStyleBenchmarkDotNet.Columns.BaselineRatioColumn→BenchmarkDotNet.Reports.MetricBenchmarkDotNet.Columns.BaselineRatioColumn→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Columns.CategoriesColumn→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Columns.CategoriesColumn→BenchmarkDotNet.Reports.SummaryStyleBenchmarkDotNet.Columns.CompositeColumnProvider→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Columns.DescriptorColumnProvider→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Columns.EmptyColumnProvider→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Columns.IColumn→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Columns.IColumn→BenchmarkDotNet.Reports.SummaryStyleBenchmarkDotNet.Columns.IColumnProvider→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Columns.IStatisticColumn→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Columns.IStatisticColumn→BenchmarkDotNet.Reports.SummaryStyleBenchmarkDotNet.Columns.JobCharacteristicColumn→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Columns.JobCharacteristicColumn→BenchmarkDotNet.Reports.SummaryStyleBenchmarkDotNet.Columns.JobColumnProvider→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Columns.LogicalGroupColumn→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Columns.LogicalGroupColumn→BenchmarkDotNet.Reports.SummaryStyleBenchmarkDotNet.Columns.MetricColumn→BenchmarkDotNet.Reports.IMetricDescriptor
- Direction
- Columns uses Reports, so a change to Reports can break Columns, while a change to Columns can't break Reports.
- Position
- Below the diagonal: Columns uses a module listed above it, which is the healthy direction.
23→22 Columns uses Configs✕
- Connections
- 1 pair of types, where a type in Columns uses a type in Configs.
- The types involved
BenchmarkDotNet.Columns.StatisticColumn→BenchmarkDotNet.Configs.ImmutableConfig
- Direction
- Columns uses Configs, so a change to Configs can break Columns, while a change to Columns can't break Configs.
- Position
- Below the diagonal: Columns uses a module listed above it, which is the healthy direction.
24→4 Attributes uses Mathematics✕
- Connections
- 1 pair of types, where a type in Attributes uses a type in Mathematics.
- The types involved
BenchmarkDotNet.Attributes.RankColumnAttribute→BenchmarkDotNet.Mathematics.NumeralSystem
- Direction
- Attributes uses Mathematics, so a change to Mathematics can break Attributes, while a change to Attributes can't break Mathematics.
- Position
- Below the diagonal: Attributes uses a module listed above it, which is the healthy direction.
24→6 Attributes uses Exporters✕
- Connections
- 3 pairs of types, where a type in Attributes uses a type in Exporters.
- The types involved
BenchmarkDotNet.Attributes.ExporterConfigBaseAttribute→BenchmarkDotNet.Exporters.IExporterBenchmarkDotNet.Attributes.JsonExporterAttribute→BenchmarkDotNet.Exporters.IExporterBenchmarkDotNet.Attributes.XmlExporterAttribute→BenchmarkDotNet.Exporters.IExporter
- Direction
- Attributes uses Exporters, so a change to Exporters can break Attributes, while a change to Attributes can't break Exporters.
- Position
- Below the diagonal: Attributes uses a module listed above it, which is the healthy direction.
24→11 Attributes uses Validators✕
- Connections
- 1 pair of types, where a type in Attributes uses a type in Validators.
- The types involved
BenchmarkDotNet.Attributes.ValidatorConfigBaseAttribute→BenchmarkDotNet.Validators.IValidator
- Direction
- Attributes uses Validators, so a change to Validators can break Attributes, while a change to Attributes can't break Validators.
- Position
- Below the diagonal: Attributes uses a module listed above it, which is the healthy direction.
24→13 Attributes uses Order✕
- Connections
- 3 pairs of types, where a type in Attributes uses a type in Order.
- The types involved
BenchmarkDotNet.Attributes.OrdererAttribute→BenchmarkDotNet.Order.JobOrderPolicyBenchmarkDotNet.Attributes.OrdererAttribute→BenchmarkDotNet.Order.MethodOrderPolicyBenchmarkDotNet.Attributes.OrdererAttribute→BenchmarkDotNet.Order.SummaryOrderPolicy
- Direction
- Attributes uses Order, so a change to Order can break Attributes, while a change to Attributes can't break Order.
- Position
- Below the diagonal: Attributes uses a module listed above it, which is the healthy direction.
24→14 Attributes uses Jobs✕
- Connections
- 4 pairs of types, where a type in Attributes uses a type in Jobs.
- The types involved
BenchmarkDotNet.Attributes.InProcessAttribute→BenchmarkDotNet.Jobs.JobBenchmarkDotNet.Attributes.JobConfigBaseAttribute→BenchmarkDotNet.Jobs.JobBenchmarkDotNet.Attributes.JobMutatorConfigBaseAttribute→BenchmarkDotNet.Jobs.JobBenchmarkDotNet.Attributes.SimpleJobAttribute→BenchmarkDotNet.Jobs.Job
- Direction
- Attributes uses Jobs, so a change to Jobs can break Attributes, while a change to Attributes can't break Jobs.
- Position
- Below the diagonal: Attributes uses a module listed above it, which is the healthy direction.
24→15 Attributes uses Environments✕
- Connections
- 12 pairs of types, where a type in Attributes uses a type in Environments.
- The types involved
BenchmarkDotNet.Attributes.DryJobAttribute→BenchmarkDotNet.Environments.JitBenchmarkDotNet.Attributes.DryJobAttribute→BenchmarkDotNet.Environments.PlatformBenchmarkDotNet.Attributes.JobConfigBaseAttribute→BenchmarkDotNet.Environments.JitBenchmarkDotNet.Attributes.JobConfigBaseAttribute→BenchmarkDotNet.Environments.PlatformBenchmarkDotNet.Attributes.LongRunJobAttribute→BenchmarkDotNet.Environments.JitBenchmarkDotNet.Attributes.LongRunJobAttribute→BenchmarkDotNet.Environments.PlatformBenchmarkDotNet.Attributes.MediumRunJobAttribute→BenchmarkDotNet.Environments.JitBenchmarkDotNet.Attributes.MediumRunJobAttribute→BenchmarkDotNet.Environments.PlatformBenchmarkDotNet.Attributes.ShortRunJobAttribute→BenchmarkDotNet.Environments.JitBenchmarkDotNet.Attributes.ShortRunJobAttribute→BenchmarkDotNet.Environments.PlatformBenchmarkDotNet.Attributes.VeryLongRunJobAttribute→BenchmarkDotNet.Environments.JitBenchmarkDotNet.Attributes.VeryLongRunJobAttribute→BenchmarkDotNet.Environments.Platform
- Direction
- Attributes uses Environments, so a change to Environments can break Attributes, while a change to Attributes can't break Environments.
- Position
- Below the diagonal: Attributes uses a module listed above it, which is the healthy direction.
24→18 Attributes uses Engines✕
- Connections
- 2 pairs of types, where a type in Attributes uses a type in Engines.
- The types involved
BenchmarkDotNet.Attributes.JitTieringAttribute→BenchmarkDotNet.Engines.JitTieringModeBenchmarkDotNet.Attributes.SimpleJobAttribute→BenchmarkDotNet.Engines.RunStrategy
- Direction
- Attributes uses Engines, so a change to Engines can break Attributes, while a change to Attributes can't break Engines.
- Position
- Below the diagonal: Attributes uses a module listed above it, which is the healthy direction.
24→22 Attributes uses Configs✕
- Connections
- 46 pairs of types, where a type in Attributes uses a type in Configs. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
BenchmarkDotNet.Attributes.ArtifactsPathAttribute→BenchmarkDotNet.Configs.IConfigBenchmarkDotNet.Attributes.ArtifactsPathAttribute→BenchmarkDotNet.Configs.IConfigSourceBenchmarkDotNet.Attributes.CategoryDiscovererAttribute→BenchmarkDotNet.Configs.IConfigBenchmarkDotNet.Attributes.CategoryDiscovererAttribute→BenchmarkDotNet.Configs.IConfigSourceBenchmarkDotNet.Attributes.ColumnConfigBaseAttribute→BenchmarkDotNet.Configs.IConfigBenchmarkDotNet.Attributes.ColumnConfigBaseAttribute→BenchmarkDotNet.Configs.IConfigSourceBenchmarkDotNet.Attributes.ConfigAttribute→BenchmarkDotNet.Configs.IConfigBenchmarkDotNet.Attributes.ConfigAttribute→BenchmarkDotNet.Configs.IConfigSourceBenchmarkDotNet.Attributes.DisassemblyDiagnoserAttribute→BenchmarkDotNet.Configs.IConfigBenchmarkDotNet.Attributes.DisassemblyDiagnoserAttribute→BenchmarkDotNet.Configs.IConfigSourceBenchmarkDotNet.Attributes.EventPipeProfilerAttribute→BenchmarkDotNet.Configs.IConfigBenchmarkDotNet.Attributes.EventPipeProfilerAttribute→BenchmarkDotNet.Configs.IConfigSourceBenchmarkDotNet.Attributes.ExceptionDiagnoserAttribute→BenchmarkDotNet.Configs.IConfigBenchmarkDotNet.Attributes.ExceptionDiagnoserAttribute→BenchmarkDotNet.Configs.IConfigSourceBenchmarkDotNet.Attributes.ExporterConfigBaseAttribute→BenchmarkDotNet.Configs.IConfigBenchmarkDotNet.Attributes.ExporterConfigBaseAttribute→BenchmarkDotNet.Configs.IConfigSourceBenchmarkDotNet.Attributes.FilterConfigBaseAttribute→BenchmarkDotNet.Configs.IConfigBenchmarkDotNet.Attributes.FilterConfigBaseAttribute→BenchmarkDotNet.Configs.IConfigSourceBenchmarkDotNet.Attributes.GroupBenchmarksByAttribute→BenchmarkDotNet.Configs.BenchmarkLogicalGroupRuleBenchmarkDotNet.Attributes.GroupBenchmarksByAttribute→BenchmarkDotNet.Configs.IConfigBenchmarkDotNet.Attributes.GroupBenchmarksByAttribute→BenchmarkDotNet.Configs.IConfigSourceBenchmarkDotNet.Attributes.HardwareCountersAttribute→BenchmarkDotNet.Configs.IConfigBenchmarkDotNet.Attributes.HardwareCountersAttribute→BenchmarkDotNet.Configs.IConfigSourceBenchmarkDotNet.Attributes.HideColumnsAttribute→BenchmarkDotNet.Configs.IConfigBenchmarkDotNet.Attributes.HideColumnsAttribute→BenchmarkDotNet.Configs.IConfigSource
- Direction
- Attributes uses Configs, so a change to Configs can break Attributes, while a change to Attributes can't break Configs.
- Position
- Below the diagonal: Attributes uses a module listed above it, which is the healthy direction.
24→23 Attributes uses Columns✕
- Connections
- 1 pair of types, where a type in Attributes uses a type in Columns.
- The types involved
BenchmarkDotNet.Attributes.ColumnConfigBaseAttribute→BenchmarkDotNet.Columns.IColumn
- Direction
- Attributes uses Columns, so a change to Columns can break Attributes, while a change to Attributes can't break Columns.
- Position
- Below the diagonal: Attributes uses a module listed above it, which is the healthy direction.
24→25 Attributes uses Diagnosers part of a loop✕
- Connections
- 3 pairs of types, where a type in Attributes uses a type in Diagnosers.
- The types involved
BenchmarkDotNet.Attributes.DisassemblyDiagnoserAttribute→BenchmarkDotNet.Diagnosers.DisassemblySyntaxBenchmarkDotNet.Attributes.EventPipeProfilerAttribute→BenchmarkDotNet.Diagnosers.EventPipeProfileBenchmarkDotNet.Attributes.HardwareCountersAttribute→BenchmarkDotNet.Diagnosers.HardwareCounter
- Direction
- Attributes uses Diagnosers, so a change to Diagnosers can break Attributes, while a change to Attributes can't break Diagnosers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→3 Diagnosers uses Disassemblers✕
- Connections
- 6 pairs of types, where a type in Diagnosers uses a type in Disassemblers.
- The types involved
BenchmarkDotNet.Diagnosers.DisassemblyDiagnoser→BenchmarkDotNet.Disassemblers.ClrMdArgsBenchmarkDotNet.Diagnosers.DisassemblyDiagnoser→BenchmarkDotNet.Disassemblers.ClrMdDisassemblerBenchmarkDotNet.Diagnosers.DisassemblyDiagnoser→BenchmarkDotNet.Disassemblers.DisassemblyResultBenchmarkDotNet.Diagnosers.DisassemblyDiagnoser→BenchmarkDotNet.Disassemblers.MonoDisassemblerBenchmarkDotNet.Diagnosers.DisassemblyDiagnoserInProcessHandler→BenchmarkDotNet.Disassemblers.ClrMdArgsBenchmarkDotNet.Diagnosers.DisassemblyDiagnoserInProcessHandler→BenchmarkDotNet.Disassemblers.DisassemblyResult
- Direction
- Diagnosers uses Disassemblers, so a change to Disassemblers can break Diagnosers, while a change to Diagnosers can't break Disassemblers.
- Position
- Below the diagonal: Diagnosers uses a module listed above it, which is the healthy direction.
25→5 Diagnosers uses Toolchains.Results✕
- Connections
- 2 pairs of types, where a type in Diagnosers uses a type in Toolchains.Results.
- The types involved
BenchmarkDotNet.Diagnosers.DiagnoserResults→BenchmarkDotNet.Toolchains.Results.BuildResultBenchmarkDotNet.Diagnosers.DiagnoserResults→BenchmarkDotNet.Toolchains.Results.ExecuteResult
- Direction
- Diagnosers uses Toolchains.Results, so a change to Toolchains.Results can break Diagnosers, while a change to Diagnosers can't break Toolchains.Results.
- Position
- Below the diagonal: Diagnosers uses a module listed above it, which is the healthy direction.
25→6 Diagnosers uses Exporters✕
- Connections
- 11 pairs of types, where a type in Diagnosers uses a type in Exporters.
- The types involved
BenchmarkDotNet.Diagnosers.CompositeDiagnoser→BenchmarkDotNet.Exporters.IExporterBenchmarkDotNet.Diagnosers.DisassemblyDiagnoser→BenchmarkDotNet.Exporters.IExporterBenchmarkDotNet.Diagnosers.EventPipeProfiler→BenchmarkDotNet.Exporters.IExporterBenchmarkDotNet.Diagnosers.ExceptionDiagnoser→BenchmarkDotNet.Exporters.IExporterBenchmarkDotNet.Diagnosers.IDiagnoser→BenchmarkDotNet.Exporters.IExporterBenchmarkDotNet.Diagnosers.MemoryDiagnoser→BenchmarkDotNet.Exporters.IExporterBenchmarkDotNet.Diagnosers.NullDiagnoser→BenchmarkDotNet.Exporters.IExporterBenchmarkDotNet.Diagnosers.PerfCollectProfiler→BenchmarkDotNet.Exporters.IExporterBenchmarkDotNet.Diagnosers.SnapshotProfilerBase→BenchmarkDotNet.Exporters.IExporterBenchmarkDotNet.Diagnosers.ThreadingDiagnoser→BenchmarkDotNet.Exporters.IExporterBenchmarkDotNet.Diagnosers.UnresolvedDiagnoser→BenchmarkDotNet.Exporters.IExporter
- Direction
- Diagnosers uses Exporters, so a change to Exporters can break Diagnosers, while a change to Diagnosers can't break Exporters.
- Position
- Below the diagonal: Diagnosers uses a module listed above it, which is the healthy direction.
25→10 Diagnosers uses Running✕
- Connections
- 18 pairs of types, where a type in Diagnosers uses a type in Running.
- The types involved
BenchmarkDotNet.Diagnosers.CompositeDiagnoser→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Diagnosers.CompositeInProcessDiagnoser→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Diagnosers.DiagnoserActionParameters→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Diagnosers.DiagnoserActionParameters→BenchmarkDotNet.Running.BenchmarkIdBenchmarkDotNet.Diagnosers.DiagnoserResults→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Diagnosers.DisassemblyDiagnoser→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Diagnosers.EventPipeProfiler→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Diagnosers.ExceptionDiagnoser→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Diagnosers.IDiagnoser→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Diagnosers.IHardwareCountersDiagnoser→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Diagnosers.IInProcessDiagnoser→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Diagnosers.InProcessDiagnoserRouter→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Diagnosers.MemoryDiagnoser→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Diagnosers.NullDiagnoser→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Diagnosers.PerfCollectProfiler→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Diagnosers.SnapshotProfilerBase→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Diagnosers.ThreadingDiagnoser→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Diagnosers.UnresolvedDiagnoser→BenchmarkDotNet.Running.BenchmarkCase
- Direction
- Diagnosers uses Running, so a change to Running can break Diagnosers, while a change to Diagnosers can't break Running.
- Position
- Below the diagonal: Diagnosers uses a module listed above it, which is the healthy direction.
25→11 Diagnosers uses Validators✕
- Connections
- 22 pairs of types, where a type in Diagnosers uses a type in Validators.
- The types involved
BenchmarkDotNet.Diagnosers.CompositeDiagnoser→BenchmarkDotNet.Validators.ValidationErrorBenchmarkDotNet.Diagnosers.CompositeDiagnoser→BenchmarkDotNet.Validators.ValidationParametersBenchmarkDotNet.Diagnosers.DisassemblyDiagnoser→BenchmarkDotNet.Validators.ValidationErrorBenchmarkDotNet.Diagnosers.DisassemblyDiagnoser→BenchmarkDotNet.Validators.ValidationParametersBenchmarkDotNet.Diagnosers.EventPipeProfiler→BenchmarkDotNet.Validators.ValidationErrorBenchmarkDotNet.Diagnosers.EventPipeProfiler→BenchmarkDotNet.Validators.ValidationParametersBenchmarkDotNet.Diagnosers.ExceptionDiagnoser→BenchmarkDotNet.Validators.ValidationErrorBenchmarkDotNet.Diagnosers.ExceptionDiagnoser→BenchmarkDotNet.Validators.ValidationParametersBenchmarkDotNet.Diagnosers.IDiagnoser→BenchmarkDotNet.Validators.ValidationErrorBenchmarkDotNet.Diagnosers.IDiagnoser→BenchmarkDotNet.Validators.ValidationParametersBenchmarkDotNet.Diagnosers.MemoryDiagnoser→BenchmarkDotNet.Validators.ValidationErrorBenchmarkDotNet.Diagnosers.MemoryDiagnoser→BenchmarkDotNet.Validators.ValidationParametersBenchmarkDotNet.Diagnosers.NullDiagnoser→BenchmarkDotNet.Validators.ValidationErrorBenchmarkDotNet.Diagnosers.NullDiagnoser→BenchmarkDotNet.Validators.ValidationParametersBenchmarkDotNet.Diagnosers.PerfCollectProfiler→BenchmarkDotNet.Validators.ValidationErrorBenchmarkDotNet.Diagnosers.PerfCollectProfiler→BenchmarkDotNet.Validators.ValidationParametersBenchmarkDotNet.Diagnosers.SnapshotProfilerBase→BenchmarkDotNet.Validators.ValidationErrorBenchmarkDotNet.Diagnosers.SnapshotProfilerBase→BenchmarkDotNet.Validators.ValidationParametersBenchmarkDotNet.Diagnosers.ThreadingDiagnoser→BenchmarkDotNet.Validators.ValidationErrorBenchmarkDotNet.Diagnosers.ThreadingDiagnoser→BenchmarkDotNet.Validators.ValidationParametersBenchmarkDotNet.Diagnosers.UnresolvedDiagnoser→BenchmarkDotNet.Validators.ValidationErrorBenchmarkDotNet.Diagnosers.UnresolvedDiagnoser→BenchmarkDotNet.Validators.ValidationParameters
- Direction
- Diagnosers uses Validators, so a change to Validators can break Diagnosers, while a change to Diagnosers can't break Validators.
- Position
- Below the diagonal: Diagnosers uses a module listed above it, which is the healthy direction.
25→15 Diagnosers uses Environments✕
- Connections
- 2 pairs of types, where a type in Diagnosers uses a type in Environments.
- The types involved
BenchmarkDotNet.Diagnosers.DisassemblyDiagnoser→BenchmarkDotNet.Environments.PlatformBenchmarkDotNet.Diagnosers.SnapshotProfilerBase→BenchmarkDotNet.Environments.Runtime
- Direction
- Diagnosers uses Environments, so a change to Environments can break Diagnosers, while a change to Diagnosers can't break Environments.
- Position
- Below the diagonal: Diagnosers uses a module listed above it, which is the healthy direction.
25→18 Diagnosers uses Engines✕
- Connections
- 18 pairs of types, where a type in Diagnosers uses a type in Engines.
- The types involved
BenchmarkDotNet.Diagnosers.CompositeDiagnoser→BenchmarkDotNet.Engines.HostSignalBenchmarkDotNet.Diagnosers.CompositeInProcessDiagnoserHandler→BenchmarkDotNet.Engines.BenchmarkSignalBenchmarkDotNet.Diagnosers.CompositeInProcessDiagnoserHandler→BenchmarkDotNet.Engines.IHostBenchmarkDotNet.Diagnosers.DiagnoserResults→BenchmarkDotNet.Engines.GcStatsBenchmarkDotNet.Diagnosers.DisassemblyDiagnoser→BenchmarkDotNet.Engines.HostSignalBenchmarkDotNet.Diagnosers.DisassemblyDiagnoserInProcessHandler→BenchmarkDotNet.Engines.BenchmarkSignalBenchmarkDotNet.Diagnosers.EventPipeProfiler→BenchmarkDotNet.Engines.HostSignalBenchmarkDotNet.Diagnosers.ExceptionDiagnoser→BenchmarkDotNet.Engines.HostSignalBenchmarkDotNet.Diagnosers.ExceptionDiagnoserInProcessHandler→BenchmarkDotNet.Engines.BenchmarkSignalBenchmarkDotNet.Diagnosers.IDiagnoser→BenchmarkDotNet.Engines.HostSignalBenchmarkDotNet.Diagnosers.IInProcessDiagnoserHandler→BenchmarkDotNet.Engines.BenchmarkSignalBenchmarkDotNet.Diagnosers.MemoryDiagnoser→BenchmarkDotNet.Engines.HostSignalBenchmarkDotNet.Diagnosers.NullDiagnoser→BenchmarkDotNet.Engines.HostSignalBenchmarkDotNet.Diagnosers.PerfCollectProfiler→BenchmarkDotNet.Engines.HostSignalBenchmarkDotNet.Diagnosers.SnapshotProfilerBase→BenchmarkDotNet.Engines.HostSignalBenchmarkDotNet.Diagnosers.ThreadingDiagnoser→BenchmarkDotNet.Engines.HostSignalBenchmarkDotNet.Diagnosers.ThreadingDiagnoserInProcessHandler→BenchmarkDotNet.Engines.BenchmarkSignalBenchmarkDotNet.Diagnosers.UnresolvedDiagnoser→BenchmarkDotNet.Engines.HostSignal
- Direction
- Diagnosers uses Engines, so a change to Engines can break Diagnosers, while a change to Diagnosers can't break Engines.
- Position
- Below the diagonal: Diagnosers uses a module listed above it, which is the healthy direction.
25→19 Diagnosers uses Reports✕
- Connections
- 30 pairs of types, where a type in Diagnosers uses a type in Reports. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
BenchmarkDotNet.Diagnosers.AllocatedMemoryMetricDescriptor→BenchmarkDotNet.Reports.IMetricDescriptorBenchmarkDotNet.Diagnosers.AllocatedMemoryMetricDescriptor→BenchmarkDotNet.Reports.MetricBenchmarkDotNet.Diagnosers.AllocatedNativeMemoryDescriptor→BenchmarkDotNet.Reports.IMetricDescriptorBenchmarkDotNet.Diagnosers.AllocatedNativeMemoryDescriptor→BenchmarkDotNet.Reports.MetricBenchmarkDotNet.Diagnosers.CompletedWorkItemCountMetricDescriptor→BenchmarkDotNet.Reports.IMetricDescriptorBenchmarkDotNet.Diagnosers.CompletedWorkItemCountMetricDescriptor→BenchmarkDotNet.Reports.MetricBenchmarkDotNet.Diagnosers.CompositeDiagnoser→BenchmarkDotNet.Reports.MetricBenchmarkDotNet.Diagnosers.DiagnoserResults→BenchmarkDotNet.Reports.MeasurementBenchmarkDotNet.Diagnosers.DisassemblyDiagnoser→BenchmarkDotNet.Reports.MetricBenchmarkDotNet.Diagnosers.EventPipeProfiler→BenchmarkDotNet.Reports.MetricBenchmarkDotNet.Diagnosers.ExceptionDiagnoser→BenchmarkDotNet.Reports.MetricBenchmarkDotNet.Diagnosers.ExceptionsFrequencyMetricDescriptor→BenchmarkDotNet.Reports.IMetricDescriptorBenchmarkDotNet.Diagnosers.ExceptionsFrequencyMetricDescriptor→BenchmarkDotNet.Reports.MetricBenchmarkDotNet.Diagnosers.GarbageCollectionsMetricDescriptor→BenchmarkDotNet.Reports.IMetricDescriptorBenchmarkDotNet.Diagnosers.GarbageCollectionsMetricDescriptor→BenchmarkDotNet.Reports.MetricBenchmarkDotNet.Diagnosers.IDiagnoser→BenchmarkDotNet.Reports.MetricBenchmarkDotNet.Diagnosers.LockContentionCountMetricDescriptor→BenchmarkDotNet.Reports.IMetricDescriptorBenchmarkDotNet.Diagnosers.LockContentionCountMetricDescriptor→BenchmarkDotNet.Reports.MetricBenchmarkDotNet.Diagnosers.MemoryDiagnoser→BenchmarkDotNet.Reports.MetricBenchmarkDotNet.Diagnosers.NativeCodeSizeMetricDescriptor→BenchmarkDotNet.Reports.IMetricDescriptorBenchmarkDotNet.Diagnosers.NativeCodeSizeMetricDescriptor→BenchmarkDotNet.Reports.MetricBenchmarkDotNet.Diagnosers.NativeMemoryLeakDescriptor→BenchmarkDotNet.Reports.IMetricDescriptorBenchmarkDotNet.Diagnosers.NativeMemoryLeakDescriptor→BenchmarkDotNet.Reports.MetricBenchmarkDotNet.Diagnosers.NullDiagnoser→BenchmarkDotNet.Reports.MetricBenchmarkDotNet.Diagnosers.PerfCollectProfiler→BenchmarkDotNet.Reports.Metric
- Direction
- Diagnosers uses Reports, so a change to Reports can break Diagnosers, while a change to Diagnosers can't break Reports.
- Position
- Below the diagonal: Diagnosers uses a module listed above it, which is the healthy direction.
25→22 Diagnosers uses Configs✕
- Connections
- 1 pair of types, where a type in Diagnosers uses a type in Configs.
- The types involved
BenchmarkDotNet.Diagnosers.DiagnoserActionParameters→BenchmarkDotNet.Configs.ImmutableConfig
- Direction
- Diagnosers uses Configs, so a change to Configs can break Diagnosers, while a change to Diagnosers can't break Configs.
- Position
- Below the diagonal: Diagnosers uses a module listed above it, which is the healthy direction.
25→23 Diagnosers uses Columns✕
- Connections
- 9 pairs of types, where a type in Diagnosers uses a type in Columns.
- The types involved
BenchmarkDotNet.Diagnosers.AllocatedMemoryMetricDescriptor→BenchmarkDotNet.Columns.UnitTypeBenchmarkDotNet.Diagnosers.AllocatedNativeMemoryDescriptor→BenchmarkDotNet.Columns.UnitTypeBenchmarkDotNet.Diagnosers.CompletedWorkItemCountMetricDescriptor→BenchmarkDotNet.Columns.UnitTypeBenchmarkDotNet.Diagnosers.ExceptionsFrequencyMetricDescriptor→BenchmarkDotNet.Columns.UnitTypeBenchmarkDotNet.Diagnosers.GarbageCollectionsMetricDescriptor→BenchmarkDotNet.Columns.UnitTypeBenchmarkDotNet.Diagnosers.LockContentionCountMetricDescriptor→BenchmarkDotNet.Columns.UnitTypeBenchmarkDotNet.Diagnosers.NativeCodeSizeMetricDescriptor→BenchmarkDotNet.Columns.UnitTypeBenchmarkDotNet.Diagnosers.NativeMemoryLeakDescriptor→BenchmarkDotNet.Columns.UnitTypeBenchmarkDotNet.Diagnosers.PmcMetricDescriptor→BenchmarkDotNet.Columns.UnitType
- Direction
- Diagnosers uses Columns, so a change to Columns can break Diagnosers, while a change to Diagnosers can't break Columns.
- Position
- Below the diagonal: Diagnosers uses a module listed above it, which is the healthy direction.
25→24 Diagnosers uses Attributes✕
- Connections
- 2 pairs of types, where a type in Diagnosers uses a type in Attributes.
- The types involved
BenchmarkDotNet.Diagnosers.ExceptionDiagnoser→BenchmarkDotNet.Attributes.ExceptionDiagnoserConfigBenchmarkDotNet.Diagnosers.ExceptionsFrequencyMetricDescriptor→BenchmarkDotNet.Attributes.ExceptionDiagnoserConfig
- Direction
- Diagnosers uses Attributes, so a change to Attributes can break Diagnosers, while a change to Diagnosers can't break Attributes.
- Position
- Below the diagonal: Diagnosers uses a module listed above it, which is the healthy direction.
25→27 Diagnosers uses Loggers part of a loop✕
- Connections
- 13 pairs of types, where a type in Diagnosers uses a type in Loggers.
- The types involved
BenchmarkDotNet.Diagnosers.CompositeDiagnoser→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Diagnosers.DisassemblyDiagnoser→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Diagnosers.EventPipeProfiler→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Diagnosers.ExceptionDiagnoser→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Diagnosers.IDiagnoser→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Diagnosers.MemoryDiagnoser→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Diagnosers.NullDiagnoser→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Diagnosers.PerfCollectProfiler→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Diagnosers.Progress→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Diagnosers.SnapshotProfilerBase→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Diagnosers.SpeedScopeExporter→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Diagnosers.ThreadingDiagnoser→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Diagnosers.UnresolvedDiagnoser→BenchmarkDotNet.Loggers.ILogger
- Direction
- Diagnosers uses Loggers, so a change to Loggers can break Diagnosers, while a change to Diagnosers can't break Loggers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→28 Diagnosers uses Analysers part of a loop✕
- Connections
- 11 pairs of types, where a type in Diagnosers uses a type in Analysers.
- The types involved
BenchmarkDotNet.Diagnosers.CompositeDiagnoser→BenchmarkDotNet.Analysers.IAnalyserBenchmarkDotNet.Diagnosers.DisassemblyDiagnoser→BenchmarkDotNet.Analysers.IAnalyserBenchmarkDotNet.Diagnosers.EventPipeProfiler→BenchmarkDotNet.Analysers.IAnalyserBenchmarkDotNet.Diagnosers.ExceptionDiagnoser→BenchmarkDotNet.Analysers.IAnalyserBenchmarkDotNet.Diagnosers.IDiagnoser→BenchmarkDotNet.Analysers.IAnalyserBenchmarkDotNet.Diagnosers.MemoryDiagnoser→BenchmarkDotNet.Analysers.IAnalyserBenchmarkDotNet.Diagnosers.NullDiagnoser→BenchmarkDotNet.Analysers.IAnalyserBenchmarkDotNet.Diagnosers.PerfCollectProfiler→BenchmarkDotNet.Analysers.IAnalyserBenchmarkDotNet.Diagnosers.SnapshotProfilerBase→BenchmarkDotNet.Analysers.IAnalyserBenchmarkDotNet.Diagnosers.ThreadingDiagnoser→BenchmarkDotNet.Analysers.IAnalyserBenchmarkDotNet.Diagnosers.UnresolvedDiagnoser→BenchmarkDotNet.Analysers.IAnalyser
- Direction
- Diagnosers uses Analysers, so a change to Analysers can break Diagnosers, while a change to Diagnosers can't break Analysers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→3 Disassemblers.Exporters uses Disassemblers✕
- Connections
- 8 pairs of types, where a type in Disassemblers.Exporters uses a type in Disassemblers.
- The types involved
BenchmarkDotNet.Disassemblers.Exporters.CombinedDisassemblyExporter→BenchmarkDotNet.Disassemblers.DisassemblyResultBenchmarkDotNet.Disassemblers.Exporters.DisassemblyPrettifier→BenchmarkDotNet.Disassemblers.DisassembledMethodBenchmarkDotNet.Disassemblers.Exporters.DisassemblyPrettifier→BenchmarkDotNet.Disassemblers.DisassemblyResultBenchmarkDotNet.Disassemblers.Exporters.Element→BenchmarkDotNet.Disassemblers.SourceCodeBenchmarkDotNet.Disassemblers.Exporters.GithubMarkdownDiffDisassemblyExporter→BenchmarkDotNet.Disassemblers.DisassemblyResultBenchmarkDotNet.Disassemblers.Exporters.GithubMarkdownDisassemblyExporter→BenchmarkDotNet.Disassemblers.DisassemblyResultBenchmarkDotNet.Disassemblers.Exporters.HtmlDisassemblyExporter→BenchmarkDotNet.Disassemblers.DisassemblyResultBenchmarkDotNet.Disassemblers.Exporters.Reference→BenchmarkDotNet.Disassemblers.SourceCode
- Direction
- Disassemblers.Exporters uses Disassemblers, so a change to Disassemblers can break Disassemblers.Exporters, while a change to Disassemblers.Exporters can't break Disassemblers.
- Position
- Below the diagonal: Disassemblers.Exporters uses a module listed above it, which is the healthy direction.
26→6 Disassemblers.Exporters uses Exporters✕
- Connections
- 4 pairs of types, where a type in Disassemblers.Exporters uses a type in Exporters.
- The types involved
BenchmarkDotNet.Disassemblers.Exporters.CombinedDisassemblyExporter→BenchmarkDotNet.Exporters.ExporterBaseBenchmarkDotNet.Disassemblers.Exporters.GithubMarkdownDiffDisassemblyExporter→BenchmarkDotNet.Exporters.ExporterBaseBenchmarkDotNet.Disassemblers.Exporters.GithubMarkdownDisassemblyExporter→BenchmarkDotNet.Exporters.ExporterBaseBenchmarkDotNet.Disassemblers.Exporters.HtmlDisassemblyExporter→BenchmarkDotNet.Exporters.ExporterBase
- Direction
- Disassemblers.Exporters uses Exporters, so a change to Exporters can break Disassemblers.Exporters, while a change to Disassemblers.Exporters can't break Exporters.
- Position
- Below the diagonal: Disassemblers.Exporters uses a module listed above it, which is the healthy direction.
26→10 Disassemblers.Exporters uses Running✕
- Connections
- 4 pairs of types, where a type in Disassemblers.Exporters uses a type in Running.
- The types involved
BenchmarkDotNet.Disassemblers.Exporters.CombinedDisassemblyExporter→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Disassemblers.Exporters.GithubMarkdownDiffDisassemblyExporter→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Disassemblers.Exporters.GithubMarkdownDisassemblyExporter→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Disassemblers.Exporters.HtmlDisassemblyExporter→BenchmarkDotNet.Running.BenchmarkCase
- Direction
- Disassemblers.Exporters uses Running, so a change to Running can break Disassemblers.Exporters, while a change to Disassemblers.Exporters can't break Running.
- Position
- Below the diagonal: Disassemblers.Exporters uses a module listed above it, which is the healthy direction.
26→17 Disassemblers.Exporters uses Helpers✕
- Connections
- 4 pairs of types, where a type in Disassemblers.Exporters uses a type in Helpers.
- The types involved
BenchmarkDotNet.Disassemblers.Exporters.CombinedDisassemblyExporter→BenchmarkDotNet.Helpers.CancelableStreamWriterBenchmarkDotNet.Disassemblers.Exporters.GithubMarkdownDiffDisassemblyExporter→BenchmarkDotNet.Helpers.CancelableStreamWriterBenchmarkDotNet.Disassemblers.Exporters.GithubMarkdownDisassemblyExporter→BenchmarkDotNet.Helpers.CancelableStreamWriterBenchmarkDotNet.Disassemblers.Exporters.HtmlDisassemblyExporter→BenchmarkDotNet.Helpers.CancelableStreamWriter
- Direction
- Disassemblers.Exporters uses Helpers, so a change to Helpers can break Disassemblers.Exporters, while a change to Disassemblers.Exporters can't break Helpers.
- Position
- Below the diagonal: Disassemblers.Exporters uses a module listed above it, which is the healthy direction.
26→19 Disassemblers.Exporters uses Reports✕
- Connections
- 5 pairs of types, where a type in Disassemblers.Exporters uses a type in Reports.
- The types involved
BenchmarkDotNet.Disassemblers.Exporters.CombinedDisassemblyExporter→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Disassemblers.Exporters.GithubMarkdownDiffDisassemblyExporter→BenchmarkDotNet.Reports.BenchmarkReportBenchmarkDotNet.Disassemblers.Exporters.GithubMarkdownDiffDisassemblyExporter→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Disassemblers.Exporters.GithubMarkdownDisassemblyExporter→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Disassemblers.Exporters.HtmlDisassemblyExporter→BenchmarkDotNet.Reports.Summary
- Direction
- Disassemblers.Exporters uses Reports, so a change to Reports can break Disassemblers.Exporters, while a change to Disassemblers.Exporters can't break Reports.
- Position
- Below the diagonal: Disassemblers.Exporters uses a module listed above it, which is the healthy direction.
26→25 Disassemblers.Exporters uses Diagnosers✕
- Connections
- 5 pairs of types, where a type in Disassemblers.Exporters uses a type in Diagnosers.
- The types involved
BenchmarkDotNet.Disassemblers.Exporters.CombinedDisassemblyExporter→BenchmarkDotNet.Diagnosers.DisassemblyDiagnoserConfigBenchmarkDotNet.Disassemblers.Exporters.DisassemblyPrettifier→BenchmarkDotNet.Diagnosers.DisassemblyDiagnoserConfigBenchmarkDotNet.Disassemblers.Exporters.GithubMarkdownDiffDisassemblyExporter→BenchmarkDotNet.Diagnosers.DisassemblyDiagnoserConfigBenchmarkDotNet.Disassemblers.Exporters.GithubMarkdownDisassemblyExporter→BenchmarkDotNet.Diagnosers.DisassemblyDiagnoserConfigBenchmarkDotNet.Disassemblers.Exporters.HtmlDisassemblyExporter→BenchmarkDotNet.Diagnosers.DisassemblyDiagnoserConfig
- Direction
- Disassemblers.Exporters uses Diagnosers, so a change to Diagnosers can break Disassemblers.Exporters, while a change to Disassemblers.Exporters can't break Diagnosers.
- Position
- Below the diagonal: Disassemblers.Exporters uses a module listed above it, which is the healthy direction.
27→10 Loggers uses Running✕
- Connections
- 2 pairs of types, where a type in Loggers uses a type in Running.
- The types involved
BenchmarkDotNet.Loggers.Broker→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Loggers.Broker→BenchmarkDotNet.Running.BenchmarkId
- Direction
- Loggers uses Running, so a change to Running can break Loggers, while a change to Loggers can't break Running.
- Position
- Below the diagonal: Loggers uses a module listed above it, which is the healthy direction.
27→17 Loggers uses Helpers✕
- Connections
- 1 pair of types, where a type in Loggers uses a type in Helpers.
- The types involved
BenchmarkDotNet.Loggers.StreamWriterWrapper→BenchmarkDotNet.Helpers.CancelableStreamWriter
- Direction
- Loggers uses Helpers, so a change to Helpers can break Loggers, while a change to Loggers can't break Helpers.
- Position
- Below the diagonal: Loggers uses a module listed above it, which is the healthy direction.
27→18 Loggers uses Engines✕
- Connections
- 1 pair of types, where a type in Loggers uses a type in Engines.
- The types involved
BenchmarkDotNet.Loggers.Broker→BenchmarkDotNet.Engines.IpcListener
- Direction
- Loggers uses Engines, so a change to Engines can break Loggers, while a change to Loggers can't break Engines.
- Position
- Below the diagonal: Loggers uses a module listed above it, which is the healthy direction.
27→25 Loggers uses Diagnosers✕
- Connections
- 3 pairs of types, where a type in Loggers uses a type in Diagnosers.
- The types involved
BenchmarkDotNet.Loggers.Broker→BenchmarkDotNet.Diagnosers.CompositeInProcessDiagnoserBenchmarkDotNet.Loggers.Broker→BenchmarkDotNet.Diagnosers.DiagnoserActionParametersBenchmarkDotNet.Loggers.Broker→BenchmarkDotNet.Diagnosers.IDiagnoser
- Direction
- Loggers uses Diagnosers, so a change to Diagnosers can break Loggers, while a change to Loggers can't break Diagnosers.
- Position
- Below the diagonal: Loggers uses a module listed above it, which is the healthy direction.
28→19 Analysers uses Reports✕
- Connections
- 19 pairs of types, where a type in Analysers uses a type in Reports.
- The types involved
BenchmarkDotNet.Analysers.AnalyserBase→BenchmarkDotNet.Reports.BenchmarkReportBenchmarkDotNet.Analysers.AnalyserBase→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Analysers.BaselineCustomAnalyzer→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Analysers.CompositeAnalyser→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Analysers.Conclusion→BenchmarkDotNet.Reports.BenchmarkReportBenchmarkDotNet.Analysers.EnvironmentAnalyser→BenchmarkDotNet.Reports.BenchmarkReportBenchmarkDotNet.Analysers.EnvironmentAnalyser→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Analysers.HideColumnsAnalyser→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Analysers.IAnalyser→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Analysers.MinIterationTimeAnalyser→BenchmarkDotNet.Reports.BenchmarkReportBenchmarkDotNet.Analysers.MinIterationTimeAnalyser→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Analysers.MultimodalDistributionAnalyzer→BenchmarkDotNet.Reports.BenchmarkReportBenchmarkDotNet.Analysers.MultimodalDistributionAnalyzer→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Analysers.OutliersAnalyser→BenchmarkDotNet.Reports.BenchmarkReportBenchmarkDotNet.Analysers.OutliersAnalyser→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Analysers.RuntimeErrorAnalyser→BenchmarkDotNet.Reports.BenchmarkReportBenchmarkDotNet.Analysers.RuntimeErrorAnalyser→BenchmarkDotNet.Reports.SummaryBenchmarkDotNet.Analysers.ZeroMeasurementAnalyser→BenchmarkDotNet.Reports.BenchmarkReportBenchmarkDotNet.Analysers.ZeroMeasurementAnalyser→BenchmarkDotNet.Reports.Summary
- Direction
- Analysers uses Reports, so a change to Reports can break Analysers, while a change to Analysers can't break Reports.
- Position
- Below the diagonal: Analysers uses a module listed above it, which is the healthy direction.
28→27 Analysers uses Loggers✕
- Connections
- 1 pair of types, where a type in Analysers uses a type in Loggers.
- The types involved
BenchmarkDotNet.Analysers.ConclusionHelper→BenchmarkDotNet.Loggers.ILogger
- Direction
- Analysers uses Loggers, so a change to Loggers can break Analysers, while a change to Analysers can't break Loggers.
- Position
- Below the diagonal: Analysers uses a module listed above it, which is the healthy direction.
29→2 Toolchains.DotNetCli uses Characteristics✕
- Connections
- 2 pairs of types, where a type in Toolchains.DotNetCli uses a type in Characteristics.
- The types involved
BenchmarkDotNet.Toolchains.DotNetCli.DotNetCliCommand→BenchmarkDotNet.Characteristics.IResolverBenchmarkDotNet.Toolchains.DotNetCli.DotNetCliExecutor→BenchmarkDotNet.Characteristics.IResolver
- Direction
- Toolchains.DotNetCli uses Characteristics, so a change to Characteristics can break Toolchains.DotNetCli, while a change to Toolchains.DotNetCli can't break Characteristics.
- Position
- Below the diagonal: Toolchains.DotNetCli uses a module listed above it, which is the healthy direction.
29→5 Toolchains.DotNetCli uses Toolchains.Results✕
- Connections
- 5 pairs of types, where a type in Toolchains.DotNetCli uses a type in Toolchains.Results.
- The types involved
BenchmarkDotNet.Toolchains.DotNetCli.DotNetCliBuilder→BenchmarkDotNet.Toolchains.Results.BuildResultBenchmarkDotNet.Toolchains.DotNetCli.DotNetCliCommand→BenchmarkDotNet.Toolchains.Results.BuildResultBenchmarkDotNet.Toolchains.DotNetCli.DotNetCliCommandResult→BenchmarkDotNet.Toolchains.Results.BuildResultBenchmarkDotNet.Toolchains.DotNetCli.DotNetCliExecutor→BenchmarkDotNet.Toolchains.Results.ExecuteResultBenchmarkDotNet.Toolchains.DotNetCli.MsBuildErrorMapper→BenchmarkDotNet.Toolchains.Results.BuildResult
- Direction
- Toolchains.DotNetCli uses Toolchains.Results, so a change to Toolchains.Results can break Toolchains.DotNetCli, while a change to Toolchains.DotNetCli can't break Toolchains.Results.
- Position
- Below the diagonal: Toolchains.DotNetCli uses a module listed above it, which is the healthy direction.
29→7 Toolchains.DotNetCli uses Toolchains.Parameters✕
- Connections
- 1 pair of types, where a type in Toolchains.DotNetCli uses a type in Toolchains.Parameters.
- The types involved
BenchmarkDotNet.Toolchains.DotNetCli.DotNetCliExecutor→BenchmarkDotNet.Toolchains.Parameters.ExecuteParameters
- Direction
- Toolchains.DotNetCli uses Toolchains.Parameters, so a change to Toolchains.Parameters can break Toolchains.DotNetCli, while a change to Toolchains.DotNetCli can't break Toolchains.Parameters.
- Position
- Below the diagonal: Toolchains.DotNetCli uses a module listed above it, which is the healthy direction.
29→8 Toolchains.DotNetCli uses ConsoleArguments✕
- Connections
- 1 pair of types, where a type in Toolchains.DotNetCli uses a type in ConsoleArguments.
- The types involved
BenchmarkDotNet.Toolchains.DotNetCli.DotNetCliSettings→BenchmarkDotNet.ConsoleArguments.CommandLineOptions
- Direction
- Toolchains.DotNetCli uses ConsoleArguments, so a change to ConsoleArguments can break Toolchains.DotNetCli, while a change to Toolchains.DotNetCli can't break ConsoleArguments.
- Position
- Below the diagonal: Toolchains.DotNetCli uses a module listed above it, which is the healthy direction.
29→9 Toolchains.DotNetCli uses Toolchains✕
- Connections
- 8 pairs of types, where a type in Toolchains.DotNetCli uses a type in Toolchains.
- The types involved
BenchmarkDotNet.Toolchains.DotNetCli.DotNetCliBuilder→BenchmarkDotNet.Toolchains.ArtifactsPathsBenchmarkDotNet.Toolchains.DotNetCli.DotNetCliBuilder→BenchmarkDotNet.Toolchains.BuilderBaseBenchmarkDotNet.Toolchains.DotNetCli.DotNetCliCommand→BenchmarkDotNet.Toolchains.ArtifactsPathsBenchmarkDotNet.Toolchains.DotNetCli.DotNetCliCommandExtensions→BenchmarkDotNet.Toolchains.ArtifactsPathsBenchmarkDotNet.Toolchains.DotNetCli.DotNetCliCommandResult→BenchmarkDotNet.Toolchains.ArtifactsPathsBenchmarkDotNet.Toolchains.DotNetCli.DotNetCliExecutor→BenchmarkDotNet.Toolchains.ArtifactsPathsBenchmarkDotNet.Toolchains.DotNetCli.DotNetCliExecutor→BenchmarkDotNet.Toolchains.IExecutorBenchmarkDotNet.Toolchains.DotNetCli.DotNetCliSettings→BenchmarkDotNet.Toolchains.ISettings
- Direction
- Toolchains.DotNetCli uses Toolchains, so a change to Toolchains can break Toolchains.DotNetCli, while a change to Toolchains.DotNetCli can't break Toolchains.
- Position
- Below the diagonal: Toolchains.DotNetCli uses a module listed above it, which is the healthy direction.
29→10 Toolchains.DotNetCli uses Running✕
- Connections
- 5 pairs of types, where a type in Toolchains.DotNetCli uses a type in Running.
- The types involved
BenchmarkDotNet.Toolchains.DotNetCli.DotNetCliBuilder→BenchmarkDotNet.Running.BuildPartitionBenchmarkDotNet.Toolchains.DotNetCli.DotNetCliCommand→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Toolchains.DotNetCli.DotNetCliCommand→BenchmarkDotNet.Running.BuildPartitionBenchmarkDotNet.Toolchains.DotNetCli.DotNetCliExecutor→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Toolchains.DotNetCli.DotNetCliExecutor→BenchmarkDotNet.Running.BenchmarkId
- Direction
- Toolchains.DotNetCli uses Running, so a change to Running can break Toolchains.DotNetCli, while a change to Toolchains.DotNetCli can't break Running.
- Position
- Below the diagonal: Toolchains.DotNetCli uses a module listed above it, which is the healthy direction.
29→14 Toolchains.DotNetCli uses Jobs✕
- Connections
- 3 pairs of types, where a type in Toolchains.DotNetCli uses a type in Jobs.
- The types involved
BenchmarkDotNet.Toolchains.DotNetCli.DotNetCliBuilder→BenchmarkDotNet.Jobs.EnvironmentVariableBenchmarkDotNet.Toolchains.DotNetCli.DotNetCliCommand→BenchmarkDotNet.Jobs.EnvironmentVariableBenchmarkDotNet.Toolchains.DotNetCli.DotNetCliCommandExecutor→BenchmarkDotNet.Jobs.EnvironmentVariable
- Direction
- Toolchains.DotNetCli uses Jobs, so a change to Jobs can break Toolchains.DotNetCli, while a change to Toolchains.DotNetCli can't break Jobs.
- Position
- Below the diagonal: Toolchains.DotNetCli uses a module listed above it, which is the healthy direction.
29→25 Toolchains.DotNetCli uses Diagnosers✕
- Connections
- 3 pairs of types, where a type in Toolchains.DotNetCli uses a type in Diagnosers.
- The types involved
BenchmarkDotNet.Toolchains.DotNetCli.DotNetCliExecutor→BenchmarkDotNet.Diagnosers.CompositeInProcessDiagnoserBenchmarkDotNet.Toolchains.DotNetCli.DotNetCliExecutor→BenchmarkDotNet.Diagnosers.IDiagnoserBenchmarkDotNet.Toolchains.DotNetCli.DotNetCliExecutor→BenchmarkDotNet.Diagnosers.RunMode
- Direction
- Toolchains.DotNetCli uses Diagnosers, so a change to Diagnosers can break Toolchains.DotNetCli, while a change to Toolchains.DotNetCli can't break Diagnosers.
- Position
- Below the diagonal: Toolchains.DotNetCli uses a module listed above it, which is the healthy direction.
29→27 Toolchains.DotNetCli uses Loggers✕
- Connections
- 4 pairs of types, where a type in Toolchains.DotNetCli uses a type in Loggers.
- The types involved
BenchmarkDotNet.Toolchains.DotNetCli.DotNetCliBuilder→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Toolchains.DotNetCli.DotNetCliCommand→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Toolchains.DotNetCli.DotNetCliCommandExecutor→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Toolchains.DotNetCli.DotNetCliExecutor→BenchmarkDotNet.Loggers.ILogger
- Direction
- Toolchains.DotNetCli uses Loggers, so a change to Loggers can break Toolchains.DotNetCli, while a change to Toolchains.DotNetCli can't break Loggers.
- Position
- Below the diagonal: Toolchains.DotNetCli uses a module listed above it, which is the healthy direction.
30→2 Toolchains.InProcess uses Characteristics✕
- Connections
- 1 pair of types, where a type in Toolchains.InProcess uses a type in Characteristics.
- The types involved
BenchmarkDotNet.Toolchains.InProcess.InProcessValidator→BenchmarkDotNet.Characteristics.Characteristic
- Direction
- Toolchains.InProcess uses Characteristics, so a change to Characteristics can break Toolchains.InProcess, while a change to Toolchains.InProcess can't break Characteristics.
- Position
- Below the diagonal: Toolchains.InProcess uses a module listed above it, which is the healthy direction.
30→10 Toolchains.InProcess uses Running✕
- Connections
- 3 pairs of types, where a type in Toolchains.InProcess uses a type in Running.
- The types involved
BenchmarkDotNet.Toolchains.InProcess.InProcessHost→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Toolchains.InProcess.InProcessHost→BenchmarkDotNet.Running.BenchmarkIdBenchmarkDotNet.Toolchains.InProcess.InProcessValidator→BenchmarkDotNet.Running.BenchmarkCase
- Direction
- Toolchains.InProcess uses Running, so a change to Running can break Toolchains.InProcess, while a change to Toolchains.InProcess can't break Running.
- Position
- Below the diagonal: Toolchains.InProcess uses a module listed above it, which is the healthy direction.
30→11 Toolchains.InProcess uses Validators✕
- Connections
- 3 pairs of types, where a type in Toolchains.InProcess uses a type in Validators.
- The types involved
BenchmarkDotNet.Toolchains.InProcess.InProcessValidator→BenchmarkDotNet.Validators.IValidatorBenchmarkDotNet.Toolchains.InProcess.InProcessValidator→BenchmarkDotNet.Validators.ValidationErrorBenchmarkDotNet.Toolchains.InProcess.InProcessValidator→BenchmarkDotNet.Validators.ValidationParameters
- Direction
- Toolchains.InProcess uses Validators, so a change to Validators can break Toolchains.InProcess, while a change to Toolchains.InProcess can't break Validators.
- Position
- Below the diagonal: Toolchains.InProcess uses a module listed above it, which is the healthy direction.
30→14 Toolchains.InProcess uses Jobs✕
- Connections
- 1 pair of types, where a type in Toolchains.InProcess uses a type in Jobs.
- The types involved
BenchmarkDotNet.Toolchains.InProcess.InProcessValidator→BenchmarkDotNet.Jobs.Job
- Direction
- Toolchains.InProcess uses Jobs, so a change to Jobs can break Toolchains.InProcess, while a change to Toolchains.InProcess can't break Jobs.
- Position
- Below the diagonal: Toolchains.InProcess uses a module listed above it, which is the healthy direction.
30→18 Toolchains.InProcess uses Engines✕
- Connections
- 3 pairs of types, where a type in Toolchains.InProcess uses a type in Engines.
- The types involved
BenchmarkDotNet.Toolchains.InProcess.InProcessHost→BenchmarkDotNet.Engines.HostSignalBenchmarkDotNet.Toolchains.InProcess.InProcessHost→BenchmarkDotNet.Engines.IHostBenchmarkDotNet.Toolchains.InProcess.InProcessHost→BenchmarkDotNet.Engines.RunResults
- Direction
- Toolchains.InProcess uses Engines, so a change to Engines can break Toolchains.InProcess, while a change to Toolchains.InProcess can't break Engines.
- Position
- Below the diagonal: Toolchains.InProcess uses a module listed above it, which is the healthy direction.
30→22 Toolchains.InProcess uses Configs✕
- Connections
- 1 pair of types, where a type in Toolchains.InProcess uses a type in Configs.
- The types involved
BenchmarkDotNet.Toolchains.InProcess.InProcessHost→BenchmarkDotNet.Configs.IConfig
- Direction
- Toolchains.InProcess uses Configs, so a change to Configs can break Toolchains.InProcess, while a change to Toolchains.InProcess can't break Configs.
- Position
- Below the diagonal: Toolchains.InProcess uses a module listed above it, which is the healthy direction.
30→25 Toolchains.InProcess uses Diagnosers✕
- Connections
- 3 pairs of types, where a type in Toolchains.InProcess uses a type in Diagnosers.
- The types involved
BenchmarkDotNet.Toolchains.InProcess.InProcessHost→BenchmarkDotNet.Diagnosers.CompositeInProcessDiagnoserBenchmarkDotNet.Toolchains.InProcess.InProcessHost→BenchmarkDotNet.Diagnosers.DiagnoserActionParametersBenchmarkDotNet.Toolchains.InProcess.InProcessHost→BenchmarkDotNet.Diagnosers.IDiagnoser
- Direction
- Toolchains.InProcess uses Diagnosers, so a change to Diagnosers can break Toolchains.InProcess, while a change to Toolchains.InProcess can't break Diagnosers.
- Position
- Below the diagonal: Toolchains.InProcess uses a module listed above it, which is the healthy direction.
30→27 Toolchains.InProcess uses Loggers✕
- Connections
- 1 pair of types, where a type in Toolchains.InProcess uses a type in Loggers.
- The types involved
BenchmarkDotNet.Toolchains.InProcess.InProcessHost→BenchmarkDotNet.Loggers.ILogger
- Direction
- Toolchains.InProcess uses Loggers, so a change to Loggers can break Toolchains.InProcess, while a change to Toolchains.InProcess can't break Loggers.
- Position
- Below the diagonal: Toolchains.InProcess uses a module listed above it, which is the healthy direction.
31→2 Toolchains.Roslyn uses Characteristics✕
- Connections
- 1 pair of types, where a type in Toolchains.Roslyn uses a type in Characteristics.
- The types involved
BenchmarkDotNet.Toolchains.Roslyn.RoslynToolchain→BenchmarkDotNet.Characteristics.IResolver
- Direction
- Toolchains.Roslyn uses Characteristics, so a change to Characteristics can break Toolchains.Roslyn, while a change to Toolchains.Roslyn can't break Characteristics.
- Position
- Below the diagonal: Toolchains.Roslyn uses a module listed above it, which is the healthy direction.
31→5 Toolchains.Roslyn uses Toolchains.Results✕
- Connections
- 1 pair of types, where a type in Toolchains.Roslyn uses a type in Toolchains.Results.
- The types involved
BenchmarkDotNet.Toolchains.Roslyn.RoslynBuilder→BenchmarkDotNet.Toolchains.Results.BuildResult
- Direction
- Toolchains.Roslyn uses Toolchains.Results, so a change to Toolchains.Results can break Toolchains.Roslyn, while a change to Toolchains.Roslyn can't break Toolchains.Results.
- Position
- Below the diagonal: Toolchains.Roslyn uses a module listed above it, which is the healthy direction.
31→9 Toolchains.Roslyn uses Toolchains✕
- Connections
- 5 pairs of types, where a type in Toolchains.Roslyn uses a type in Toolchains.
- The types involved
BenchmarkDotNet.Toolchains.Roslyn.RoslynBuilder→BenchmarkDotNet.Toolchains.ArtifactsPathsBenchmarkDotNet.Toolchains.Roslyn.RoslynBuilder→BenchmarkDotNet.Toolchains.BuilderBaseBenchmarkDotNet.Toolchains.Roslyn.RoslynToolchain→BenchmarkDotNet.Toolchains.IBuilderBenchmarkDotNet.Toolchains.Roslyn.RoslynToolchain→BenchmarkDotNet.Toolchains.IExecutorBenchmarkDotNet.Toolchains.Roslyn.RoslynToolchain→BenchmarkDotNet.Toolchains.Toolchain
- Direction
- Toolchains.Roslyn uses Toolchains, so a change to Toolchains can break Toolchains.Roslyn, while a change to Toolchains.Roslyn can't break Toolchains.
- Position
- Below the diagonal: Toolchains.Roslyn uses a module listed above it, which is the healthy direction.
31→10 Toolchains.Roslyn uses Running✕
- Connections
- 3 pairs of types, where a type in Toolchains.Roslyn uses a type in Running.
- The types involved
BenchmarkDotNet.Toolchains.Roslyn.RoslynBuilder→BenchmarkDotNet.Running.BenchmarkBuildInfoBenchmarkDotNet.Toolchains.Roslyn.RoslynBuilder→BenchmarkDotNet.Running.BuildPartitionBenchmarkDotNet.Toolchains.Roslyn.RoslynToolchain→BenchmarkDotNet.Running.BenchmarkCase
- Direction
- Toolchains.Roslyn uses Running, so a change to Running can break Toolchains.Roslyn, while a change to Toolchains.Roslyn can't break Running.
- Position
- Below the diagonal: Toolchains.Roslyn uses a module listed above it, which is the healthy direction.
31→11 Toolchains.Roslyn uses Validators✕
- Connections
- 1 pair of types, where a type in Toolchains.Roslyn uses a type in Validators.
- The types involved
BenchmarkDotNet.Toolchains.Roslyn.RoslynToolchain→BenchmarkDotNet.Validators.ValidationError
- Direction
- Toolchains.Roslyn uses Validators, so a change to Validators can break Toolchains.Roslyn, while a change to Toolchains.Roslyn can't break Validators.
- Position
- Below the diagonal: Toolchains.Roslyn uses a module listed above it, which is the healthy direction.
31→15 Toolchains.Roslyn uses Environments✕
- Connections
- 2 pairs of types, where a type in Toolchains.Roslyn uses a type in Environments.
- The types involved
BenchmarkDotNet.Toolchains.Roslyn.RoslynBuilder→BenchmarkDotNet.Environments.PlatformBenchmarkDotNet.Toolchains.Roslyn.RoslynToolchain→BenchmarkDotNet.Environments.Runtime
- Direction
- Toolchains.Roslyn uses Environments, so a change to Environments can break Toolchains.Roslyn, while a change to Toolchains.Roslyn can't break Environments.
- Position
- Below the diagonal: Toolchains.Roslyn uses a module listed above it, which is the healthy direction.
31→27 Toolchains.Roslyn uses Loggers✕
- Connections
- 1 pair of types, where a type in Toolchains.Roslyn uses a type in Loggers.
- The types involved
BenchmarkDotNet.Toolchains.Roslyn.RoslynBuilder→BenchmarkDotNet.Loggers.ILogger
- Direction
- Toolchains.Roslyn uses Loggers, so a change to Loggers can break Toolchains.Roslyn, while a change to Toolchains.Roslyn can't break Loggers.
- Position
- Below the diagonal: Toolchains.Roslyn uses a module listed above it, which is the healthy direction.
32→6 Diagnostics.Windows uses Exporters✕
- Connections
- 4 pairs of types, where a type in Diagnostics.Windows uses a type in Exporters.
- The types involved
BenchmarkDotNet.Diagnostics.Windows.ConcurrencyVisualizerProfiler→BenchmarkDotNet.Exporters.IExporterBenchmarkDotNet.Diagnostics.Windows.EtwDiagnoser→BenchmarkDotNet.Exporters.IExporterBenchmarkDotNet.Diagnostics.Windows.EtwProfiler→BenchmarkDotNet.Exporters.IExporterBenchmarkDotNet.Diagnostics.Windows.NativeMemoryProfiler→BenchmarkDotNet.Exporters.IExporter
- Direction
- Diagnostics.Windows uses Exporters, so a change to Exporters can break Diagnostics.Windows, while a change to Diagnostics.Windows can't break Exporters.
- Position
- Below the diagonal: Diagnostics.Windows uses a module listed above it, which is the healthy direction.
32→10 Diagnostics.Windows uses Running✕
- Connections
- 9 pairs of types, where a type in Diagnostics.Windows uses a type in Running.
- The types involved
BenchmarkDotNet.Diagnostics.Windows.ConcurrencyVisualizerProfiler→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Diagnostics.Windows.EtwDiagnoser→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Diagnostics.Windows.EtwProfiler→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Diagnostics.Windows.InliningDiagnoser→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Diagnostics.Windows.JitDiagnoser→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Diagnostics.Windows.JitStatsDiagnoser→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Diagnostics.Windows.NativeMemoryProfiler→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Diagnostics.Windows.Session→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Diagnostics.Windows.TailCallDiagnoser→BenchmarkDotNet.Running.BenchmarkCase
- Direction
- Diagnostics.Windows uses Running, so a change to Running can break Diagnostics.Windows, while a change to Diagnostics.Windows can't break Running.
- Position
- Below the diagonal: Diagnostics.Windows uses a module listed above it, which is the healthy direction.
32→11 Diagnostics.Windows uses Validators✕
- Connections
- 10 pairs of types, where a type in Diagnostics.Windows uses a type in Validators.
- The types involved
BenchmarkDotNet.Diagnostics.Windows.ConcurrencyVisualizerProfiler→BenchmarkDotNet.Validators.ValidationErrorBenchmarkDotNet.Diagnostics.Windows.ConcurrencyVisualizerProfiler→BenchmarkDotNet.Validators.ValidationParametersBenchmarkDotNet.Diagnostics.Windows.EtwProfiler→BenchmarkDotNet.Validators.ValidationErrorBenchmarkDotNet.Diagnostics.Windows.EtwProfiler→BenchmarkDotNet.Validators.ValidationParametersBenchmarkDotNet.Diagnostics.Windows.HardwareCounters→BenchmarkDotNet.Validators.ValidationErrorBenchmarkDotNet.Diagnostics.Windows.HardwareCounters→BenchmarkDotNet.Validators.ValidationParametersBenchmarkDotNet.Diagnostics.Windows.JitDiagnoser→BenchmarkDotNet.Validators.ValidationErrorBenchmarkDotNet.Diagnostics.Windows.JitDiagnoser→BenchmarkDotNet.Validators.ValidationParametersBenchmarkDotNet.Diagnostics.Windows.NativeMemoryProfiler→BenchmarkDotNet.Validators.ValidationErrorBenchmarkDotNet.Diagnostics.Windows.NativeMemoryProfiler→BenchmarkDotNet.Validators.ValidationParameters
- Direction
- Diagnostics.Windows uses Validators, so a change to Validators can break Diagnostics.Windows, while a change to Diagnostics.Windows can't break Validators.
- Position
- Below the diagonal: Diagnostics.Windows uses a module listed above it, which is the healthy direction.
32→12 Diagnostics.Windows uses Parameters✕
- Connections
- 1 pair of types, where a type in Diagnostics.Windows uses a type in Parameters.
- The types involved
BenchmarkDotNet.Diagnostics.Windows.EtwDiagnoser→BenchmarkDotNet.Parameters.ParameterInstances
- Direction
- Diagnostics.Windows uses Parameters, so a change to Parameters can break Diagnostics.Windows, while a change to Diagnostics.Windows can't break Parameters.
- Position
- Below the diagonal: Diagnostics.Windows uses a module listed above it, which is the healthy direction.
32→17 Diagnostics.Windows uses Helpers✕
- Connections
- 2 pairs of types, where a type in Diagnostics.Windows uses a type in Helpers.
- The types involved
BenchmarkDotNet.Diagnostics.Windows.EtwDiagnoser→BenchmarkDotNet.Helpers.DisposeAtProcessTerminationBenchmarkDotNet.Diagnostics.Windows.Session→BenchmarkDotNet.Helpers.DisposeAtProcessTermination
- Direction
- Diagnostics.Windows uses Helpers, so a change to Helpers can break Diagnostics.Windows, while a change to Diagnostics.Windows can't break Helpers.
- Position
- Below the diagonal: Diagnostics.Windows uses a module listed above it, which is the healthy direction.
32→18 Diagnostics.Windows uses Engines✕
- Connections
- 4 pairs of types, where a type in Diagnostics.Windows uses a type in Engines.
- The types involved
BenchmarkDotNet.Diagnostics.Windows.ConcurrencyVisualizerProfiler→BenchmarkDotNet.Engines.HostSignalBenchmarkDotNet.Diagnostics.Windows.EtwProfiler→BenchmarkDotNet.Engines.HostSignalBenchmarkDotNet.Diagnostics.Windows.JitDiagnoser→BenchmarkDotNet.Engines.HostSignalBenchmarkDotNet.Diagnostics.Windows.NativeMemoryProfiler→BenchmarkDotNet.Engines.HostSignal
- Direction
- Diagnostics.Windows uses Engines, so a change to Engines can break Diagnostics.Windows, while a change to Diagnostics.Windows can't break Engines.
- Position
- Below the diagonal: Diagnostics.Windows uses a module listed above it, which is the healthy direction.
32→19 Diagnostics.Windows uses Reports✕
- Connections
- 11 pairs of types, where a type in Diagnostics.Windows uses a type in Reports.
- The types involved
BenchmarkDotNet.Diagnostics.Windows.ConcurrencyVisualizerProfiler→BenchmarkDotNet.Reports.MetricBenchmarkDotNet.Diagnostics.Windows.EtwProfiler→BenchmarkDotNet.Reports.MetricBenchmarkDotNet.Diagnostics.Windows.JitAllocatedMemoryDescriptor→BenchmarkDotNet.Reports.IMetricDescriptorBenchmarkDotNet.Diagnostics.Windows.JitAllocatedMemoryDescriptor→BenchmarkDotNet.Reports.MetricBenchmarkDotNet.Diagnostics.Windows.JitDiagnoser→BenchmarkDotNet.Reports.MetricBenchmarkDotNet.Diagnostics.Windows.JitStatsDiagnoser→BenchmarkDotNet.Reports.MetricBenchmarkDotNet.Diagnostics.Windows.MethodsJittedDescriptor→BenchmarkDotNet.Reports.IMetricDescriptorBenchmarkDotNet.Diagnostics.Windows.MethodsJittedDescriptor→BenchmarkDotNet.Reports.MetricBenchmarkDotNet.Diagnostics.Windows.MethodsTieredDescriptor→BenchmarkDotNet.Reports.IMetricDescriptorBenchmarkDotNet.Diagnostics.Windows.MethodsTieredDescriptor→BenchmarkDotNet.Reports.MetricBenchmarkDotNet.Diagnostics.Windows.NativeMemoryProfiler→BenchmarkDotNet.Reports.Metric
- Direction
- Diagnostics.Windows uses Reports, so a change to Reports can break Diagnostics.Windows, while a change to Diagnostics.Windows can't break Reports.
- Position
- Below the diagonal: Diagnostics.Windows uses a module listed above it, which is the healthy direction.
32→23 Diagnostics.Windows uses Columns✕
- Connections
- 3 pairs of types, where a type in Diagnostics.Windows uses a type in Columns.
- The types involved
BenchmarkDotNet.Diagnostics.Windows.JitAllocatedMemoryDescriptor→BenchmarkDotNet.Columns.UnitTypeBenchmarkDotNet.Diagnostics.Windows.MethodsJittedDescriptor→BenchmarkDotNet.Columns.UnitTypeBenchmarkDotNet.Diagnostics.Windows.MethodsTieredDescriptor→BenchmarkDotNet.Columns.UnitType
- Direction
- Diagnostics.Windows uses Columns, so a change to Columns can break Diagnostics.Windows, while a change to Diagnostics.Windows can't break Columns.
- Position
- Below the diagonal: Diagnostics.Windows uses a module listed above it, which is the healthy direction.
32→25 Diagnostics.Windows uses Diagnosers✕
- Connections
- 33 pairs of types, where a type in Diagnostics.Windows uses a type in Diagnosers. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
BenchmarkDotNet.Diagnostics.Windows.ConcurrencyVisualizerProfiler→BenchmarkDotNet.Diagnosers.DiagnoserActionParametersBenchmarkDotNet.Diagnostics.Windows.ConcurrencyVisualizerProfiler→BenchmarkDotNet.Diagnosers.DiagnoserResultsBenchmarkDotNet.Diagnostics.Windows.ConcurrencyVisualizerProfiler→BenchmarkDotNet.Diagnosers.IProfilerBenchmarkDotNet.Diagnostics.Windows.ConcurrencyVisualizerProfiler→BenchmarkDotNet.Diagnosers.RunModeBenchmarkDotNet.Diagnostics.Windows.EtwDiagnoser→BenchmarkDotNet.Diagnosers.DiagnoserActionParametersBenchmarkDotNet.Diagnostics.Windows.EtwDiagnoser→BenchmarkDotNet.Diagnosers.RunModeBenchmarkDotNet.Diagnostics.Windows.EtwProfiler→BenchmarkDotNet.Diagnosers.DiagnoserActionParametersBenchmarkDotNet.Diagnostics.Windows.EtwProfiler→BenchmarkDotNet.Diagnosers.DiagnoserResultsBenchmarkDotNet.Diagnostics.Windows.EtwProfiler→BenchmarkDotNet.Diagnosers.IDiagnoserBenchmarkDotNet.Diagnostics.Windows.EtwProfiler→BenchmarkDotNet.Diagnosers.IHardwareCountersDiagnoserBenchmarkDotNet.Diagnostics.Windows.EtwProfiler→BenchmarkDotNet.Diagnosers.IProfilerBenchmarkDotNet.Diagnostics.Windows.EtwProfiler→BenchmarkDotNet.Diagnosers.PmcStatsBenchmarkDotNet.Diagnostics.Windows.EtwProfiler→BenchmarkDotNet.Diagnosers.PreciseMachineCounterBenchmarkDotNet.Diagnostics.Windows.EtwProfiler→BenchmarkDotNet.Diagnosers.RunModeBenchmarkDotNet.Diagnostics.Windows.EtwProfilerConfig→BenchmarkDotNet.Diagnosers.HardwareCounterBenchmarkDotNet.Diagnostics.Windows.HardwareCounters→BenchmarkDotNet.Diagnosers.HardwareCounterBenchmarkDotNet.Diagnostics.Windows.HardwareCounters→BenchmarkDotNet.Diagnosers.PreciseMachineCounterBenchmarkDotNet.Diagnostics.Windows.HeapSession→BenchmarkDotNet.Diagnosers.DiagnoserActionParametersBenchmarkDotNet.Diagnostics.Windows.InliningDiagnoser→BenchmarkDotNet.Diagnosers.IProfilerBenchmarkDotNet.Diagnostics.Windows.JitDiagnoser→BenchmarkDotNet.Diagnosers.DiagnoserActionParametersBenchmarkDotNet.Diagnostics.Windows.JitDiagnoser→BenchmarkDotNet.Diagnosers.DiagnoserResultsBenchmarkDotNet.Diagnostics.Windows.JitDiagnoser→BenchmarkDotNet.Diagnosers.IDiagnoserBenchmarkDotNet.Diagnostics.Windows.JitDiagnoser→BenchmarkDotNet.Diagnosers.RunModeBenchmarkDotNet.Diagnostics.Windows.JitStatsDiagnoser→BenchmarkDotNet.Diagnosers.DiagnoserResultsBenchmarkDotNet.Diagnostics.Windows.JitStatsDiagnoser→BenchmarkDotNet.Diagnosers.IProfiler
- Direction
- Diagnostics.Windows uses Diagnosers, so a change to Diagnosers can break Diagnostics.Windows, while a change to Diagnostics.Windows can't break Diagnosers.
- Position
- Below the diagonal: Diagnostics.Windows uses a module listed above it, which is the healthy direction.
32→27 Diagnostics.Windows uses Loggers✕
- Connections
- 6 pairs of types, where a type in Diagnostics.Windows uses a type in Loggers.
- The types involved
BenchmarkDotNet.Diagnostics.Windows.ConcurrencyVisualizerProfiler→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Diagnostics.Windows.EtwDiagnoser→BenchmarkDotNet.Loggers.LogCaptureBenchmarkDotNet.Diagnostics.Windows.EtwProfiler→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Diagnostics.Windows.JitDiagnoser→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Diagnostics.Windows.NativeMemoryProfiler→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Diagnostics.Windows.NativeMemoryProfiler→BenchmarkDotNet.Loggers.LogCapture
- Direction
- Diagnostics.Windows uses Loggers, so a change to Loggers can break Diagnostics.Windows, while a change to Diagnostics.Windows can't break Loggers.
- Position
- Below the diagonal: Diagnostics.Windows uses a module listed above it, which is the healthy direction.
32→28 Diagnostics.Windows uses Analysers✕
- Connections
- 4 pairs of types, where a type in Diagnostics.Windows uses a type in Analysers.
- The types involved
BenchmarkDotNet.Diagnostics.Windows.ConcurrencyVisualizerProfiler→BenchmarkDotNet.Analysers.IAnalyserBenchmarkDotNet.Diagnostics.Windows.EtwDiagnoser→BenchmarkDotNet.Analysers.IAnalyserBenchmarkDotNet.Diagnostics.Windows.EtwProfiler→BenchmarkDotNet.Analysers.IAnalyserBenchmarkDotNet.Diagnostics.Windows.NativeMemoryProfiler→BenchmarkDotNet.Analysers.IAnalyser
- Direction
- Diagnostics.Windows uses Analysers, so a change to Analysers can break Diagnostics.Windows, while a change to Diagnostics.Windows can't break Analysers.
- Position
- Below the diagonal: Diagnostics.Windows uses a module listed above it, which is the healthy direction.
33→2 Toolchains.CsProj uses Characteristics✕
- Connections
- 1 pair of types, where a type in Toolchains.CsProj uses a type in Characteristics.
- The types involved
BenchmarkDotNet.Toolchains.CsProj.CsProjNetToolchain→BenchmarkDotNet.Characteristics.IResolver
- Direction
- Toolchains.CsProj uses Characteristics, so a change to Characteristics can break Toolchains.CsProj, while a change to Toolchains.CsProj can't break Characteristics.
- Position
- Below the diagonal: Toolchains.CsProj uses a module listed above it, which is the healthy direction.
33→9 Toolchains.CsProj uses Toolchains✕
- Connections
- 6 pairs of types, where a type in Toolchains.CsProj uses a type in Toolchains.
- The types involved
BenchmarkDotNet.Toolchains.CsProj.CsProjBuilder→BenchmarkDotNet.Toolchains.ArtifactsPathsBenchmarkDotNet.Toolchains.CsProj.CsProjNetToolchain→BenchmarkDotNet.Toolchains.IBuilderBenchmarkDotNet.Toolchains.CsProj.CsProjNetToolchain→BenchmarkDotNet.Toolchains.IExecutorBenchmarkDotNet.Toolchains.CsProj.CsProjNetToolchain→BenchmarkDotNet.Toolchains.IHasSettingsBenchmarkDotNet.Toolchains.CsProj.CsProjNetToolchain→BenchmarkDotNet.Toolchains.ISettingsBenchmarkDotNet.Toolchains.CsProj.CsProjNetToolchain→BenchmarkDotNet.Toolchains.Toolchain
- Direction
- Toolchains.CsProj uses Toolchains, so a change to Toolchains can break Toolchains.CsProj, while a change to Toolchains.CsProj can't break Toolchains.
- Position
- Below the diagonal: Toolchains.CsProj uses a module listed above it, which is the healthy direction.
33→10 Toolchains.CsProj uses Running✕
- Connections
- 2 pairs of types, where a type in Toolchains.CsProj uses a type in Running.
- The types involved
BenchmarkDotNet.Toolchains.CsProj.CsProjBuilder→BenchmarkDotNet.Running.BuildPartitionBenchmarkDotNet.Toolchains.CsProj.CsProjNetToolchain→BenchmarkDotNet.Running.BenchmarkCase
- Direction
- Toolchains.CsProj uses Running, so a change to Running can break Toolchains.CsProj, while a change to Toolchains.CsProj can't break Running.
- Position
- Below the diagonal: Toolchains.CsProj uses a module listed above it, which is the healthy direction.
33→11 Toolchains.CsProj uses Validators✕
- Connections
- 1 pair of types, where a type in Toolchains.CsProj uses a type in Validators.
- The types involved
BenchmarkDotNet.Toolchains.CsProj.CsProjNetToolchain→BenchmarkDotNet.Validators.ValidationError
- Direction
- Toolchains.CsProj uses Validators, so a change to Validators can break Toolchains.CsProj, while a change to Toolchains.CsProj can't break Validators.
- Position
- Below the diagonal: Toolchains.CsProj uses a module listed above it, which is the healthy direction.
33→15 Toolchains.CsProj uses Environments✕
- Connections
- 1 pair of types, where a type in Toolchains.CsProj uses a type in Environments.
- The types involved
BenchmarkDotNet.Toolchains.CsProj.CsProjNetToolchain→BenchmarkDotNet.Environments.Runtime
- Direction
- Toolchains.CsProj uses Environments, so a change to Environments can break Toolchains.CsProj, while a change to Toolchains.CsProj can't break Environments.
- Position
- Below the diagonal: Toolchains.CsProj uses a module listed above it, which is the healthy direction.
33→27 Toolchains.CsProj uses Loggers✕
- Connections
- 1 pair of types, where a type in Toolchains.CsProj uses a type in Loggers.
- The types involved
BenchmarkDotNet.Toolchains.CsProj.CsProjBuilder→BenchmarkDotNet.Loggers.ILogger
- Direction
- Toolchains.CsProj uses Loggers, so a change to Loggers can break Toolchains.CsProj, while a change to Toolchains.CsProj can't break Loggers.
- Position
- Below the diagonal: Toolchains.CsProj uses a module listed above it, which is the healthy direction.
33→29 Toolchains.CsProj uses Toolchains.DotNetCli✕
- Connections
- 3 pairs of types, where a type in Toolchains.CsProj uses a type in Toolchains.DotNetCli.
- The types involved
BenchmarkDotNet.Toolchains.CsProj.CsProjBuilder→BenchmarkDotNet.Toolchains.DotNetCli.DotNetCliBuilderBenchmarkDotNet.Toolchains.CsProj.CsProjBuilder→BenchmarkDotNet.Toolchains.DotNetCli.DotNetCliSettingsBenchmarkDotNet.Toolchains.CsProj.CsProjNetToolchain→BenchmarkDotNet.Toolchains.DotNetCli.DotNetCliSettings
- Direction
- Toolchains.CsProj uses Toolchains.DotNetCli, so a change to Toolchains.DotNetCli can break Toolchains.CsProj, while a change to Toolchains.CsProj can't break Toolchains.DotNetCli.
- Position
- Below the diagonal: Toolchains.CsProj uses a module listed above it, which is the healthy direction.
34→5 Toolchains.InProcess.Emit uses Toolchains.Results✕
- Connections
- 2 pairs of types, where a type in Toolchains.InProcess.Emit uses a type in Toolchains.Results.
- The types involved
BenchmarkDotNet.Toolchains.InProcess.Emit.InProcessEmitBuilder→BenchmarkDotNet.Toolchains.Results.BuildResultBenchmarkDotNet.Toolchains.InProcess.Emit.InProcessEmitExecutor→BenchmarkDotNet.Toolchains.Results.ExecuteResult
- Direction
- Toolchains.InProcess.Emit uses Toolchains.Results, so a change to Toolchains.Results can break Toolchains.InProcess.Emit, while a change to Toolchains.InProcess.Emit can't break Toolchains.Results.
- Position
- Below the diagonal: Toolchains.InProcess.Emit uses a module listed above it, which is the healthy direction.
34→7 Toolchains.InProcess.Emit uses Toolchains.Parameters✕
- Connections
- 2 pairs of types, where a type in Toolchains.InProcess.Emit uses a type in Toolchains.Parameters.
- The types involved
BenchmarkDotNet.Toolchains.InProcess.Emit.InProcessEmitExecutor→BenchmarkDotNet.Toolchains.Parameters.ExecuteParametersBenchmarkDotNet.Toolchains.InProcess.Emit.InProcessEmitRunner→BenchmarkDotNet.Toolchains.Parameters.ExecuteParameters
- Direction
- Toolchains.InProcess.Emit uses Toolchains.Parameters, so a change to Toolchains.Parameters can break Toolchains.InProcess.Emit, while a change to Toolchains.InProcess.Emit can't break Toolchains.Parameters.
- Position
- Below the diagonal: Toolchains.InProcess.Emit uses a module listed above it, which is the healthy direction.
34→9 Toolchains.InProcess.Emit uses Toolchains✕
- Connections
- 5 pairs of types, where a type in Toolchains.InProcess.Emit uses a type in Toolchains.
- The types involved
BenchmarkDotNet.Toolchains.InProcess.Emit.InProcessEmitArtifactsPath→BenchmarkDotNet.Toolchains.ArtifactsPathsBenchmarkDotNet.Toolchains.InProcess.Emit.InProcessEmitBuilder→BenchmarkDotNet.Toolchains.ArtifactsPathsBenchmarkDotNet.Toolchains.InProcess.Emit.InProcessEmitBuilder→BenchmarkDotNet.Toolchains.IBuilderBenchmarkDotNet.Toolchains.InProcess.Emit.InProcessEmitExecutor→BenchmarkDotNet.Toolchains.IExecutorBenchmarkDotNet.Toolchains.InProcess.Emit.InProcessEmitToolchain→BenchmarkDotNet.Toolchains.Toolchain
- Direction
- Toolchains.InProcess.Emit uses Toolchains, so a change to Toolchains can break Toolchains.InProcess.Emit, while a change to Toolchains.InProcess.Emit can't break Toolchains.
- Position
- Below the diagonal: Toolchains.InProcess.Emit uses a module listed above it, which is the healthy direction.
34→10 Toolchains.InProcess.Emit uses Running✕
- Connections
- 2 pairs of types, where a type in Toolchains.InProcess.Emit uses a type in Running.
- The types involved
BenchmarkDotNet.Toolchains.InProcess.Emit.InProcessEmitBuilder→BenchmarkDotNet.Running.BuildPartitionBenchmarkDotNet.Toolchains.InProcess.Emit.InProcessEmitRunner→BenchmarkDotNet.Running.BenchmarkCase
- Direction
- Toolchains.InProcess.Emit uses Running, so a change to Running can break Toolchains.InProcess.Emit, while a change to Toolchains.InProcess.Emit can't break Running.
- Position
- Below the diagonal: Toolchains.InProcess.Emit uses a module listed above it, which is the healthy direction.
34→15 Toolchains.InProcess.Emit uses Environments✕
- Connections
- 1 pair of types, where a type in Toolchains.InProcess.Emit uses a type in Environments.
- The types involved
BenchmarkDotNet.Toolchains.InProcess.Emit.InProcessEmitToolchain→BenchmarkDotNet.Environments.Runtime
- Direction
- Toolchains.InProcess.Emit uses Environments, so a change to Environments can break Toolchains.InProcess.Emit, while a change to Toolchains.InProcess.Emit can't break Environments.
- Position
- Below the diagonal: Toolchains.InProcess.Emit uses a module listed above it, which is the healthy direction.
34→18 Toolchains.InProcess.Emit uses Engines✕
- Connections
- 2 pairs of types, where a type in Toolchains.InProcess.Emit uses a type in Engines.
- The types involved
BenchmarkDotNet.Toolchains.InProcess.Emit.InProcessEmitExecutor→BenchmarkDotNet.Engines.IHostBenchmarkDotNet.Toolchains.InProcess.Emit.InProcessEmitRunner→BenchmarkDotNet.Engines.IHost
- Direction
- Toolchains.InProcess.Emit uses Engines, so a change to Engines can break Toolchains.InProcess.Emit, while a change to Toolchains.InProcess.Emit can't break Engines.
- Position
- Below the diagonal: Toolchains.InProcess.Emit uses a module listed above it, which is the healthy direction.
34→27 Toolchains.InProcess.Emit uses Loggers✕
- Connections
- 1 pair of types, where a type in Toolchains.InProcess.Emit uses a type in Loggers.
- The types involved
BenchmarkDotNet.Toolchains.InProcess.Emit.InProcessEmitBuilder→BenchmarkDotNet.Loggers.ILogger
- Direction
- Toolchains.InProcess.Emit uses Loggers, so a change to Loggers can break Toolchains.InProcess.Emit, while a change to Toolchains.InProcess.Emit can't break Loggers.
- Position
- Below the diagonal: Toolchains.InProcess.Emit uses a module listed above it, which is the healthy direction.
34→30 Toolchains.InProcess.Emit uses Toolchains.InProcess✕
- Connections
- 1 pair of types, where a type in Toolchains.InProcess.Emit uses a type in Toolchains.InProcess.
- The types involved
BenchmarkDotNet.Toolchains.InProcess.Emit.InProcessEmitSettings→BenchmarkDotNet.Toolchains.InProcess.InProcessSettings
- Direction
- Toolchains.InProcess.Emit uses Toolchains.InProcess, so a change to Toolchains.InProcess can break Toolchains.InProcess.Emit, while a change to Toolchains.InProcess.Emit can't break Toolchains.InProcess.
- Position
- Below the diagonal: Toolchains.InProcess.Emit uses a module listed above it, which is the healthy direction.
35→2 Toolchains.InProcess.NoEmit uses Characteristics✕
- Connections
- 1 pair of types, where a type in Toolchains.InProcess.NoEmit uses a type in Characteristics.
- The types involved
BenchmarkDotNet.Toolchains.InProcess.NoEmit.InProcessNoEmitToolchain→BenchmarkDotNet.Characteristics.IResolver
- Direction
- Toolchains.InProcess.NoEmit uses Characteristics, so a change to Characteristics can break Toolchains.InProcess.NoEmit, while a change to Toolchains.InProcess.NoEmit can't break Characteristics.
- Position
- Below the diagonal: Toolchains.InProcess.NoEmit uses a module listed above it, which is the healthy direction.
35→5 Toolchains.InProcess.NoEmit uses Toolchains.Results✕
- Connections
- 2 pairs of types, where a type in Toolchains.InProcess.NoEmit uses a type in Toolchains.Results.
- The types involved
BenchmarkDotNet.Toolchains.InProcess.NoEmit.InProcessNoEmitBuilder→BenchmarkDotNet.Toolchains.Results.BuildResultBenchmarkDotNet.Toolchains.InProcess.NoEmit.InProcessNoEmitExecutor→BenchmarkDotNet.Toolchains.Results.ExecuteResult
- Direction
- Toolchains.InProcess.NoEmit uses Toolchains.Results, so a change to Toolchains.Results can break Toolchains.InProcess.NoEmit, while a change to Toolchains.InProcess.NoEmit can't break Toolchains.Results.
- Position
- Below the diagonal: Toolchains.InProcess.NoEmit uses a module listed above it, which is the healthy direction.
35→7 Toolchains.InProcess.NoEmit uses Toolchains.Parameters✕
- Connections
- 3 pairs of types, where a type in Toolchains.InProcess.NoEmit uses a type in Toolchains.Parameters.
- The types involved
BenchmarkDotNet.Toolchains.InProcess.NoEmit.InProcessNoEmitExecutor→BenchmarkDotNet.Toolchains.Parameters.ExecuteParametersBenchmarkDotNet.Toolchains.InProcess.NoEmit.InProcessNoEmitRunner→BenchmarkDotNet.Toolchains.Parameters.ExecuteParametersBenchmarkDotNet.Toolchains.InProcess.NoEmit.Runnable→BenchmarkDotNet.Toolchains.Parameters.ExecuteParameters
- Direction
- Toolchains.InProcess.NoEmit uses Toolchains.Parameters, so a change to Toolchains.Parameters can break Toolchains.InProcess.NoEmit, while a change to Toolchains.InProcess.NoEmit can't break Toolchains.Parameters.
- Position
- Below the diagonal: Toolchains.InProcess.NoEmit uses a module listed above it, which is the healthy direction.
35→9 Toolchains.InProcess.NoEmit uses Toolchains✕
- Connections
- 5 pairs of types, where a type in Toolchains.InProcess.NoEmit uses a type in Toolchains.
- The types involved
BenchmarkDotNet.Toolchains.InProcess.NoEmit.InProcessNoEmitBuilder→BenchmarkDotNet.Toolchains.IBuilderBenchmarkDotNet.Toolchains.InProcess.NoEmit.InProcessNoEmitExecutor→BenchmarkDotNet.Toolchains.IExecutorBenchmarkDotNet.Toolchains.InProcess.NoEmit.InProcessNoEmitToolchain→BenchmarkDotNet.Toolchains.IBuilderBenchmarkDotNet.Toolchains.InProcess.NoEmit.InProcessNoEmitToolchain→BenchmarkDotNet.Toolchains.IExecutorBenchmarkDotNet.Toolchains.InProcess.NoEmit.InProcessNoEmitToolchain→BenchmarkDotNet.Toolchains.IToolchain
- Direction
- Toolchains.InProcess.NoEmit uses Toolchains, so a change to Toolchains can break Toolchains.InProcess.NoEmit, while a change to Toolchains.InProcess.NoEmit can't break Toolchains.
- Position
- Below the diagonal: Toolchains.InProcess.NoEmit uses a module listed above it, which is the healthy direction.
35→10 Toolchains.InProcess.NoEmit uses Running✕
- Connections
- 4 pairs of types, where a type in Toolchains.InProcess.NoEmit uses a type in Running.
- The types involved
BenchmarkDotNet.Toolchains.InProcess.NoEmit.BenchmarkActionFactory→BenchmarkDotNet.Running.DescriptorBenchmarkDotNet.Toolchains.InProcess.NoEmit.InProcessNoEmitBuilder→BenchmarkDotNet.Running.BuildPartitionBenchmarkDotNet.Toolchains.InProcess.NoEmit.InProcessNoEmitRunner→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Toolchains.InProcess.NoEmit.InProcessNoEmitToolchain→BenchmarkDotNet.Running.BenchmarkCase
- Direction
- Toolchains.InProcess.NoEmit uses Running, so a change to Running can break Toolchains.InProcess.NoEmit, while a change to Toolchains.InProcess.NoEmit can't break Running.
- Position
- Below the diagonal: Toolchains.InProcess.NoEmit uses a module listed above it, which is the healthy direction.
35→11 Toolchains.InProcess.NoEmit uses Validators✕
- Connections
- 1 pair of types, where a type in Toolchains.InProcess.NoEmit uses a type in Validators.
- The types involved
BenchmarkDotNet.Toolchains.InProcess.NoEmit.InProcessNoEmitToolchain→BenchmarkDotNet.Validators.ValidationError
- Direction
- Toolchains.InProcess.NoEmit uses Validators, so a change to Validators can break Toolchains.InProcess.NoEmit, while a change to Toolchains.InProcess.NoEmit can't break Validators.
- Position
- Below the diagonal: Toolchains.InProcess.NoEmit uses a module listed above it, which is the healthy direction.
35→15 Toolchains.InProcess.NoEmit uses Environments✕
- Connections
- 1 pair of types, where a type in Toolchains.InProcess.NoEmit uses a type in Environments.
- The types involved
BenchmarkDotNet.Toolchains.InProcess.NoEmit.InProcessNoEmitToolchain→BenchmarkDotNet.Environments.Runtime
- Direction
- Toolchains.InProcess.NoEmit uses Environments, so a change to Environments can break Toolchains.InProcess.NoEmit, while a change to Toolchains.InProcess.NoEmit can't break Environments.
- Position
- Below the diagonal: Toolchains.InProcess.NoEmit uses a module listed above it, which is the healthy direction.
35→18 Toolchains.InProcess.NoEmit uses Engines✕
- Connections
- 7 pairs of types, where a type in Toolchains.InProcess.NoEmit uses a type in Engines.
- The types involved
BenchmarkDotNet.Toolchains.InProcess.NoEmit.BenchmarkActionAsyncEnumerable→BenchmarkDotNet.Engines.WorkloadValueTaskSourceBenchmarkDotNet.Toolchains.InProcess.NoEmit.BenchmarkActionConfiguredCancelableAsyncEnumerable→BenchmarkDotNet.Engines.WorkloadValueTaskSourceBenchmarkDotNet.Toolchains.InProcess.NoEmit.BenchmarkActionTask→BenchmarkDotNet.Engines.WorkloadValueTaskSourceBenchmarkDotNet.Toolchains.InProcess.NoEmit.BenchmarkActionValueTask→BenchmarkDotNet.Engines.WorkloadValueTaskSourceBenchmarkDotNet.Toolchains.InProcess.NoEmit.InProcessNoEmitExecutor→BenchmarkDotNet.Engines.IHostBenchmarkDotNet.Toolchains.InProcess.NoEmit.InProcessNoEmitRunner→BenchmarkDotNet.Engines.IHostBenchmarkDotNet.Toolchains.InProcess.NoEmit.Runnable→BenchmarkDotNet.Engines.IHost
- Direction
- Toolchains.InProcess.NoEmit uses Engines, so a change to Engines can break Toolchains.InProcess.NoEmit, while a change to Toolchains.InProcess.NoEmit can't break Engines.
- Position
- Below the diagonal: Toolchains.InProcess.NoEmit uses a module listed above it, which is the healthy direction.
35→27 Toolchains.InProcess.NoEmit uses Loggers✕
- Connections
- 1 pair of types, where a type in Toolchains.InProcess.NoEmit uses a type in Loggers.
- The types involved
BenchmarkDotNet.Toolchains.InProcess.NoEmit.InProcessNoEmitBuilder→BenchmarkDotNet.Loggers.ILogger
- Direction
- Toolchains.InProcess.NoEmit uses Loggers, so a change to Loggers can break Toolchains.InProcess.NoEmit, while a change to Toolchains.InProcess.NoEmit can't break Loggers.
- Position
- Below the diagonal: Toolchains.InProcess.NoEmit uses a module listed above it, which is the healthy direction.
35→30 Toolchains.InProcess.NoEmit uses Toolchains.InProcess✕
- Connections
- 1 pair of types, where a type in Toolchains.InProcess.NoEmit uses a type in Toolchains.InProcess.
- The types involved
BenchmarkDotNet.Toolchains.InProcess.NoEmit.InProcessNoEmitSettings→BenchmarkDotNet.Toolchains.InProcess.InProcessSettings
- Direction
- Toolchains.InProcess.NoEmit uses Toolchains.InProcess, so a change to Toolchains.InProcess can break Toolchains.InProcess.NoEmit, while a change to Toolchains.InProcess.NoEmit can't break Toolchains.InProcess.
- Position
- Below the diagonal: Toolchains.InProcess.NoEmit uses a module listed above it, which is the healthy direction.
36→2 Toolchains.CoreRun uses Characteristics✕
- Connections
- 1 pair of types, where a type in Toolchains.CoreRun uses a type in Characteristics.
- The types involved
BenchmarkDotNet.Toolchains.CoreRun.CoreRunToolchain→BenchmarkDotNet.Characteristics.IResolver
- Direction
- Toolchains.CoreRun uses Characteristics, so a change to Characteristics can break Toolchains.CoreRun, while a change to Toolchains.CoreRun can't break Characteristics.
- Position
- Below the diagonal: Toolchains.CoreRun uses a module listed above it, which is the healthy direction.
36→5 Toolchains.CoreRun uses Toolchains.Results✕
- Connections
- 1 pair of types, where a type in Toolchains.CoreRun uses a type in Toolchains.Results.
- The types involved
BenchmarkDotNet.Toolchains.CoreRun.CoreRunBuilder→BenchmarkDotNet.Toolchains.Results.BuildResult
- Direction
- Toolchains.CoreRun uses Toolchains.Results, so a change to Toolchains.Results can break Toolchains.CoreRun, while a change to Toolchains.CoreRun can't break Toolchains.Results.
- Position
- Below the diagonal: Toolchains.CoreRun uses a module listed above it, which is the healthy direction.
36→8 Toolchains.CoreRun uses ConsoleArguments✕
- Connections
- 1 pair of types, where a type in Toolchains.CoreRun uses a type in ConsoleArguments.
- The types involved
BenchmarkDotNet.Toolchains.CoreRun.CoreRunSettings→BenchmarkDotNet.ConsoleArguments.CommandLineOptions
- Direction
- Toolchains.CoreRun uses ConsoleArguments, so a change to ConsoleArguments can break Toolchains.CoreRun, while a change to Toolchains.CoreRun can't break ConsoleArguments.
- Position
- Below the diagonal: Toolchains.CoreRun uses a module listed above it, which is the healthy direction.
36→9 Toolchains.CoreRun uses Toolchains✕
- Connections
- 6 pairs of types, where a type in Toolchains.CoreRun uses a type in Toolchains.
- The types involved
BenchmarkDotNet.Toolchains.CoreRun.CoreRunBuilder→BenchmarkDotNet.Toolchains.ArtifactsPathsBenchmarkDotNet.Toolchains.CoreRun.CoreRunToolchain→BenchmarkDotNet.Toolchains.IBuilderBenchmarkDotNet.Toolchains.CoreRun.CoreRunToolchain→BenchmarkDotNet.Toolchains.IExecutorBenchmarkDotNet.Toolchains.CoreRun.CoreRunToolchain→BenchmarkDotNet.Toolchains.IHasSettingsBenchmarkDotNet.Toolchains.CoreRun.CoreRunToolchain→BenchmarkDotNet.Toolchains.ISettingsBenchmarkDotNet.Toolchains.CoreRun.CoreRunToolchain→BenchmarkDotNet.Toolchains.IToolchain
- Direction
- Toolchains.CoreRun uses Toolchains, so a change to Toolchains can break Toolchains.CoreRun, while a change to Toolchains.CoreRun can't break Toolchains.
- Position
- Below the diagonal: Toolchains.CoreRun uses a module listed above it, which is the healthy direction.
36→10 Toolchains.CoreRun uses Running✕
- Connections
- 2 pairs of types, where a type in Toolchains.CoreRun uses a type in Running.
- The types involved
BenchmarkDotNet.Toolchains.CoreRun.CoreRunBuilder→BenchmarkDotNet.Running.BuildPartitionBenchmarkDotNet.Toolchains.CoreRun.CoreRunToolchain→BenchmarkDotNet.Running.BenchmarkCase
- Direction
- Toolchains.CoreRun uses Running, so a change to Running can break Toolchains.CoreRun, while a change to Toolchains.CoreRun can't break Running.
- Position
- Below the diagonal: Toolchains.CoreRun uses a module listed above it, which is the healthy direction.
36→11 Toolchains.CoreRun uses Validators✕
- Connections
- 1 pair of types, where a type in Toolchains.CoreRun uses a type in Validators.
- The types involved
BenchmarkDotNet.Toolchains.CoreRun.CoreRunToolchain→BenchmarkDotNet.Validators.ValidationError
- Direction
- Toolchains.CoreRun uses Validators, so a change to Validators can break Toolchains.CoreRun, while a change to Toolchains.CoreRun can't break Validators.
- Position
- Below the diagonal: Toolchains.CoreRun uses a module listed above it, which is the healthy direction.
36→15 Toolchains.CoreRun uses Environments✕
- Connections
- 1 pair of types, where a type in Toolchains.CoreRun uses a type in Environments.
- The types involved
BenchmarkDotNet.Toolchains.CoreRun.CoreRunToolchain→BenchmarkDotNet.Environments.Runtime
- Direction
- Toolchains.CoreRun uses Environments, so a change to Environments can break Toolchains.CoreRun, while a change to Toolchains.CoreRun can't break Environments.
- Position
- Below the diagonal: Toolchains.CoreRun uses a module listed above it, which is the healthy direction.
36→27 Toolchains.CoreRun uses Loggers✕
- Connections
- 1 pair of types, where a type in Toolchains.CoreRun uses a type in Loggers.
- The types involved
BenchmarkDotNet.Toolchains.CoreRun.CoreRunBuilder→BenchmarkDotNet.Loggers.ILogger
- Direction
- Toolchains.CoreRun uses Loggers, so a change to Loggers can break Toolchains.CoreRun, while a change to Toolchains.CoreRun can't break Loggers.
- Position
- Below the diagonal: Toolchains.CoreRun uses a module listed above it, which is the healthy direction.
36→29 Toolchains.CoreRun uses Toolchains.DotNetCli✕
- Connections
- 1 pair of types, where a type in Toolchains.CoreRun uses a type in Toolchains.DotNetCli.
- The types involved
BenchmarkDotNet.Toolchains.CoreRun.CoreRunSettings→BenchmarkDotNet.Toolchains.DotNetCli.DotNetCliSettings
- Direction
- Toolchains.CoreRun uses Toolchains.DotNetCli, so a change to Toolchains.DotNetCli can break Toolchains.CoreRun, while a change to Toolchains.CoreRun can't break Toolchains.DotNetCli.
- Position
- Below the diagonal: Toolchains.CoreRun uses a module listed above it, which is the healthy direction.
36→33 Toolchains.CoreRun uses Toolchains.CsProj✕
- Connections
- 1 pair of types, where a type in Toolchains.CoreRun uses a type in Toolchains.CsProj.
- The types involved
BenchmarkDotNet.Toolchains.CoreRun.CoreRunBuilder→BenchmarkDotNet.Toolchains.CsProj.CsProjBuilder
- Direction
- Toolchains.CoreRun uses Toolchains.CsProj, so a change to Toolchains.CsProj can break Toolchains.CoreRun, while a change to Toolchains.CoreRun can't break Toolchains.CsProj.
- Position
- Below the diagonal: Toolchains.CoreRun uses a module listed above it, which is the healthy direction.
37→2 Toolchains.Framework uses Characteristics✕
- Connections
- 1 pair of types, where a type in Toolchains.Framework uses a type in Characteristics.
- The types involved
BenchmarkDotNet.Toolchains.Framework.CsProjFrameworkToolchain→BenchmarkDotNet.Characteristics.IResolver
- Direction
- Toolchains.Framework uses Characteristics, so a change to Characteristics can break Toolchains.Framework, while a change to Toolchains.Framework can't break Characteristics.
- Position
- Below the diagonal: Toolchains.Framework uses a module listed above it, which is the healthy direction.
37→8 Toolchains.Framework uses ConsoleArguments✕
- Connections
- 1 pair of types, where a type in Toolchains.Framework uses a type in ConsoleArguments.
- The types involved
BenchmarkDotNet.Toolchains.Framework.FrameworkSettings→BenchmarkDotNet.ConsoleArguments.CommandLineOptions
- Direction
- Toolchains.Framework uses ConsoleArguments, so a change to ConsoleArguments can break Toolchains.Framework, while a change to Toolchains.Framework can't break ConsoleArguments.
- Position
- Below the diagonal: Toolchains.Framework uses a module listed above it, which is the healthy direction.
37→9 Toolchains.Framework uses Toolchains✕
- Connections
- 3 pairs of types, where a type in Toolchains.Framework uses a type in Toolchains.
- The types involved
BenchmarkDotNet.Toolchains.Framework.CsProjFrameworkToolchain→BenchmarkDotNet.Toolchains.IHasSettingsBenchmarkDotNet.Toolchains.Framework.CsProjFrameworkToolchain→BenchmarkDotNet.Toolchains.ISettingsBenchmarkDotNet.Toolchains.Framework.CsProjFrameworkToolchain→BenchmarkDotNet.Toolchains.Toolchain
- Direction
- Toolchains.Framework uses Toolchains, so a change to Toolchains can break Toolchains.Framework, while a change to Toolchains.Framework can't break Toolchains.
- Position
- Below the diagonal: Toolchains.Framework uses a module listed above it, which is the healthy direction.
37→10 Toolchains.Framework uses Running✕
- Connections
- 1 pair of types, where a type in Toolchains.Framework uses a type in Running.
- The types involved
BenchmarkDotNet.Toolchains.Framework.CsProjFrameworkToolchain→BenchmarkDotNet.Running.BenchmarkCase
- Direction
- Toolchains.Framework uses Running, so a change to Running can break Toolchains.Framework, while a change to Toolchains.Framework can't break Running.
- Position
- Below the diagonal: Toolchains.Framework uses a module listed above it, which is the healthy direction.
37→11 Toolchains.Framework uses Validators✕
- Connections
- 1 pair of types, where a type in Toolchains.Framework uses a type in Validators.
- The types involved
BenchmarkDotNet.Toolchains.Framework.CsProjFrameworkToolchain→BenchmarkDotNet.Validators.ValidationError
- Direction
- Toolchains.Framework uses Validators, so a change to Validators can break Toolchains.Framework, while a change to Toolchains.Framework can't break Validators.
- Position
- Below the diagonal: Toolchains.Framework uses a module listed above it, which is the healthy direction.
37→15 Toolchains.Framework uses Environments✕
- Connections
- 2 pairs of types, where a type in Toolchains.Framework uses a type in Environments.
- The types involved
BenchmarkDotNet.Toolchains.Framework.CsProjFrameworkToolchain→BenchmarkDotNet.Environments.ClrRuntimeBenchmarkDotNet.Toolchains.Framework.RoslynFrameworkToolchain→BenchmarkDotNet.Environments.ClrRuntime
- Direction
- Toolchains.Framework uses Environments, so a change to Environments can break Toolchains.Framework, while a change to Toolchains.Framework can't break Environments.
- Position
- Below the diagonal: Toolchains.Framework uses a module listed above it, which is the healthy direction.
37→29 Toolchains.Framework uses Toolchains.DotNetCli✕
- Connections
- 2 pairs of types, where a type in Toolchains.Framework uses a type in Toolchains.DotNetCli.
- The types involved
BenchmarkDotNet.Toolchains.Framework.CsProjFrameworkBuilder→BenchmarkDotNet.Toolchains.DotNetCli.DotNetCliSettingsBenchmarkDotNet.Toolchains.Framework.FrameworkSettings→BenchmarkDotNet.Toolchains.DotNetCli.DotNetCliSettings
- Direction
- Toolchains.Framework uses Toolchains.DotNetCli, so a change to Toolchains.DotNetCli can break Toolchains.Framework, while a change to Toolchains.Framework can't break Toolchains.DotNetCli.
- Position
- Below the diagonal: Toolchains.Framework uses a module listed above it, which is the healthy direction.
37→31 Toolchains.Framework uses Toolchains.Roslyn✕
- Connections
- 1 pair of types, where a type in Toolchains.Framework uses a type in Toolchains.Roslyn.
- The types involved
BenchmarkDotNet.Toolchains.Framework.RoslynFrameworkToolchain→BenchmarkDotNet.Toolchains.Roslyn.RoslynToolchain
- Direction
- Toolchains.Framework uses Toolchains.Roslyn, so a change to Toolchains.Roslyn can break Toolchains.Framework, while a change to Toolchains.Framework can't break Toolchains.Roslyn.
- Position
- Below the diagonal: Toolchains.Framework uses a module listed above it, which is the healthy direction.
37→33 Toolchains.Framework uses Toolchains.CsProj✕
- Connections
- 1 pair of types, where a type in Toolchains.Framework uses a type in Toolchains.CsProj.
- The types involved
BenchmarkDotNet.Toolchains.Framework.CsProjFrameworkBuilder→BenchmarkDotNet.Toolchains.CsProj.CsProjBuilder
- Direction
- Toolchains.Framework uses Toolchains.CsProj, so a change to Toolchains.CsProj can break Toolchains.Framework, while a change to Toolchains.Framework can't break Toolchains.CsProj.
- Position
- Below the diagonal: Toolchains.Framework uses a module listed above it, which is the healthy direction.
38→2 Toolchains.Mono uses Characteristics✕
- Connections
- 3 pairs of types, where a type in Toolchains.Mono uses a type in Characteristics.
- The types involved
BenchmarkDotNet.Toolchains.Mono.LegacyMonoExecutor→BenchmarkDotNet.Characteristics.IResolverBenchmarkDotNet.Toolchains.Mono.RoslynMonoAotToolchain→BenchmarkDotNet.Characteristics.IResolverBenchmarkDotNet.Toolchains.Mono.RoslynMonoToolchain→BenchmarkDotNet.Characteristics.IResolver
- Direction
- Toolchains.Mono uses Characteristics, so a change to Characteristics can break Toolchains.Mono, while a change to Toolchains.Mono can't break Characteristics.
- Position
- Below the diagonal: Toolchains.Mono uses a module listed above it, which is the healthy direction.
38→5 Toolchains.Mono uses Toolchains.Results✕
- Connections
- 1 pair of types, where a type in Toolchains.Mono uses a type in Toolchains.Results.
- The types involved
BenchmarkDotNet.Toolchains.Mono.LegacyMonoAotBuilder→BenchmarkDotNet.Toolchains.Results.BuildResult
- Direction
- Toolchains.Mono uses Toolchains.Results, so a change to Toolchains.Results can break Toolchains.Mono, while a change to Toolchains.Mono can't break Toolchains.Results.
- Position
- Below the diagonal: Toolchains.Mono uses a module listed above it, which is the healthy direction.
38→8 Toolchains.Mono uses ConsoleArguments✕
- Connections
- 4 pairs of types, where a type in Toolchains.Mono uses a type in ConsoleArguments.
- The types involved
BenchmarkDotNet.Toolchains.Mono.LegacyMonoSettings→BenchmarkDotNet.ConsoleArguments.CommandLineOptionsBenchmarkDotNet.Toolchains.Mono.MonoAotSettings→BenchmarkDotNet.ConsoleArguments.CommandLineOptionsBenchmarkDotNet.Toolchains.Mono.MonoCoreSettings→BenchmarkDotNet.ConsoleArguments.CommandLineOptionsBenchmarkDotNet.Toolchains.Mono.MonoSettings→BenchmarkDotNet.ConsoleArguments.CommandLineOptions
- Direction
- Toolchains.Mono uses ConsoleArguments, so a change to ConsoleArguments can break Toolchains.Mono, while a change to Toolchains.Mono can't break ConsoleArguments.
- Position
- Below the diagonal: Toolchains.Mono uses a module listed above it, which is the healthy direction.
38→9 Toolchains.Mono uses Toolchains✕
- Connections
- 9 pairs of types, where a type in Toolchains.Mono uses a type in Toolchains.
- The types involved
BenchmarkDotNet.Toolchains.Mono.CsProjMonoBuilder→BenchmarkDotNet.Toolchains.ArtifactsPathsBenchmarkDotNet.Toolchains.Mono.LegacyMonoAotBuilder→BenchmarkDotNet.Toolchains.ArtifactsPathsBenchmarkDotNet.Toolchains.Mono.LegacyMonoExecutor→BenchmarkDotNet.Toolchains.ArtifactsPathsBenchmarkDotNet.Toolchains.Mono.LegacyMonoExecutor→BenchmarkDotNet.Toolchains.ExecutorBenchmarkDotNet.Toolchains.Mono.LegacyMonoSettings→BenchmarkDotNet.Toolchains.ISettingsBenchmarkDotNet.Toolchains.Mono.RoslynMonoAotToolchain→BenchmarkDotNet.Toolchains.IHasSettingsBenchmarkDotNet.Toolchains.Mono.RoslynMonoAotToolchain→BenchmarkDotNet.Toolchains.ISettingsBenchmarkDotNet.Toolchains.Mono.RoslynMonoToolchain→BenchmarkDotNet.Toolchains.IHasSettingsBenchmarkDotNet.Toolchains.Mono.RoslynMonoToolchain→BenchmarkDotNet.Toolchains.ISettings
- Direction
- Toolchains.Mono uses Toolchains, so a change to Toolchains can break Toolchains.Mono, while a change to Toolchains.Mono can't break Toolchains.
- Position
- Below the diagonal: Toolchains.Mono uses a module listed above it, which is the healthy direction.
38→10 Toolchains.Mono uses Running✕
- Connections
- 5 pairs of types, where a type in Toolchains.Mono uses a type in Running.
- The types involved
BenchmarkDotNet.Toolchains.Mono.CsProjMonoBuilder→BenchmarkDotNet.Running.BuildPartitionBenchmarkDotNet.Toolchains.Mono.LegacyMonoAotBuilder→BenchmarkDotNet.Running.BuildPartitionBenchmarkDotNet.Toolchains.Mono.LegacyMonoExecutor→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Toolchains.Mono.RoslynMonoAotToolchain→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Toolchains.Mono.RoslynMonoToolchain→BenchmarkDotNet.Running.BenchmarkCase
- Direction
- Toolchains.Mono uses Running, so a change to Running can break Toolchains.Mono, while a change to Toolchains.Mono can't break Running.
- Position
- Below the diagonal: Toolchains.Mono uses a module listed above it, which is the healthy direction.
38→11 Toolchains.Mono uses Validators✕
- Connections
- 2 pairs of types, where a type in Toolchains.Mono uses a type in Validators.
- The types involved
BenchmarkDotNet.Toolchains.Mono.RoslynMonoAotToolchain→BenchmarkDotNet.Validators.ValidationErrorBenchmarkDotNet.Toolchains.Mono.RoslynMonoToolchain→BenchmarkDotNet.Validators.ValidationError
- Direction
- Toolchains.Mono uses Validators, so a change to Validators can break Toolchains.Mono, while a change to Toolchains.Mono can't break Validators.
- Position
- Below the diagonal: Toolchains.Mono uses a module listed above it, which is the healthy direction.
38→14 Toolchains.Mono uses Jobs✕
- Connections
- 1 pair of types, where a type in Toolchains.Mono uses a type in Jobs.
- The types involved
BenchmarkDotNet.Toolchains.Mono.LegacyMonoExecutor→BenchmarkDotNet.Jobs.Job
- Direction
- Toolchains.Mono uses Jobs, so a change to Jobs can break Toolchains.Mono, while a change to Toolchains.Mono can't break Jobs.
- Position
- Below the diagonal: Toolchains.Mono uses a module listed above it, which is the healthy direction.
38→15 Toolchains.Mono uses Environments✕
- Connections
- 1 pair of types, where a type in Toolchains.Mono uses a type in Environments.
- The types involved
BenchmarkDotNet.Toolchains.Mono.CsProjMonoCoreToolchain→BenchmarkDotNet.Environments.MonoCoreRuntime
- Direction
- Toolchains.Mono uses Environments, so a change to Environments can break Toolchains.Mono, while a change to Toolchains.Mono can't break Environments.
- Position
- Below the diagonal: Toolchains.Mono uses a module listed above it, which is the healthy direction.
38→27 Toolchains.Mono uses Loggers✕
- Connections
- 1 pair of types, where a type in Toolchains.Mono uses a type in Loggers.
- The types involved
BenchmarkDotNet.Toolchains.Mono.LegacyMonoAotBuilder→BenchmarkDotNet.Loggers.ILogger
- Direction
- Toolchains.Mono uses Loggers, so a change to Loggers can break Toolchains.Mono, while a change to Toolchains.Mono can't break Loggers.
- Position
- Below the diagonal: Toolchains.Mono uses a module listed above it, which is the healthy direction.
38→29 Toolchains.Mono uses Toolchains.DotNetCli✕
- Connections
- 1 pair of types, where a type in Toolchains.Mono uses a type in Toolchains.DotNetCli.
- The types involved
BenchmarkDotNet.Toolchains.Mono.MonoCoreSettings→BenchmarkDotNet.Toolchains.DotNetCli.DotNetCliSettings
- Direction
- Toolchains.Mono uses Toolchains.DotNetCli, so a change to Toolchains.DotNetCli can break Toolchains.Mono, while a change to Toolchains.Mono can't break Toolchains.DotNetCli.
- Position
- Below the diagonal: Toolchains.Mono uses a module listed above it, which is the healthy direction.
38→31 Toolchains.Mono uses Toolchains.Roslyn✕
- Connections
- 3 pairs of types, where a type in Toolchains.Mono uses a type in Toolchains.Roslyn.
- The types involved
BenchmarkDotNet.Toolchains.Mono.LegacyMonoAotBuilder→BenchmarkDotNet.Toolchains.Roslyn.RoslynBuilderBenchmarkDotNet.Toolchains.Mono.RoslynMonoAotToolchain→BenchmarkDotNet.Toolchains.Roslyn.RoslynToolchainBenchmarkDotNet.Toolchains.Mono.RoslynMonoToolchain→BenchmarkDotNet.Toolchains.Roslyn.RoslynToolchain
- Direction
- Toolchains.Mono uses Toolchains.Roslyn, so a change to Toolchains.Roslyn can break Toolchains.Mono, while a change to Toolchains.Mono can't break Toolchains.Roslyn.
- Position
- Below the diagonal: Toolchains.Mono uses a module listed above it, which is the healthy direction.
38→33 Toolchains.Mono uses Toolchains.CsProj✕
- Connections
- 2 pairs of types, where a type in Toolchains.Mono uses a type in Toolchains.CsProj.
- The types involved
BenchmarkDotNet.Toolchains.Mono.CsProjMonoBuilder→BenchmarkDotNet.Toolchains.CsProj.CsProjBuilderBenchmarkDotNet.Toolchains.Mono.CsProjMonoCoreToolchain→BenchmarkDotNet.Toolchains.CsProj.CsProjNetToolchain
- Direction
- Toolchains.Mono uses Toolchains.CsProj, so a change to Toolchains.CsProj can break Toolchains.Mono, while a change to Toolchains.Mono can't break Toolchains.CsProj.
- Position
- Below the diagonal: Toolchains.Mono uses a module listed above it, which is the healthy direction.
39→8 Toolchains.NativeAot uses ConsoleArguments✕
- Connections
- 1 pair of types, where a type in Toolchains.NativeAot uses a type in ConsoleArguments.
- The types involved
BenchmarkDotNet.Toolchains.NativeAot.NativeAotSettings→BenchmarkDotNet.ConsoleArguments.CommandLineOptions
- Direction
- Toolchains.NativeAot uses ConsoleArguments, so a change to ConsoleArguments can break Toolchains.NativeAot, while a change to Toolchains.NativeAot can't break ConsoleArguments.
- Position
- Below the diagonal: Toolchains.NativeAot uses a module listed above it, which is the healthy direction.
39→9 Toolchains.NativeAot uses Toolchains✕
- Connections
- 1 pair of types, where a type in Toolchains.NativeAot uses a type in Toolchains.
- The types involved
BenchmarkDotNet.Toolchains.NativeAot.CsProjNativeAotBuilder→BenchmarkDotNet.Toolchains.ArtifactsPaths
- Direction
- Toolchains.NativeAot uses Toolchains, so a change to Toolchains can break Toolchains.NativeAot, while a change to Toolchains.NativeAot can't break Toolchains.
- Position
- Below the diagonal: Toolchains.NativeAot uses a module listed above it, which is the healthy direction.
39→10 Toolchains.NativeAot uses Running✕
- Connections
- 1 pair of types, where a type in Toolchains.NativeAot uses a type in Running.
- The types involved
BenchmarkDotNet.Toolchains.NativeAot.CsProjNativeAotBuilder→BenchmarkDotNet.Running.BuildPartition
- Direction
- Toolchains.NativeAot uses Running, so a change to Running can break Toolchains.NativeAot, while a change to Toolchains.NativeAot can't break Running.
- Position
- Below the diagonal: Toolchains.NativeAot uses a module listed above it, which is the healthy direction.
39→15 Toolchains.NativeAot uses Environments✕
- Connections
- 2 pairs of types, where a type in Toolchains.NativeAot uses a type in Environments.
- The types involved
BenchmarkDotNet.Toolchains.NativeAot.CsProjNativeAotBuilder→BenchmarkDotNet.Environments.PlatformBenchmarkDotNet.Toolchains.NativeAot.CsProjNativeAotToolchain→BenchmarkDotNet.Environments.NativeAotRuntime
- Direction
- Toolchains.NativeAot uses Environments, so a change to Environments can break Toolchains.NativeAot, while a change to Toolchains.NativeAot can't break Environments.
- Position
- Below the diagonal: Toolchains.NativeAot uses a module listed above it, which is the healthy direction.
39→27 Toolchains.NativeAot uses Loggers✕
- Connections
- 1 pair of types, where a type in Toolchains.NativeAot uses a type in Loggers.
- The types involved
BenchmarkDotNet.Toolchains.NativeAot.CsProjNativeAotBuilder→BenchmarkDotNet.Loggers.ILogger
- Direction
- Toolchains.NativeAot uses Loggers, so a change to Loggers can break Toolchains.NativeAot, while a change to Toolchains.NativeAot can't break Loggers.
- Position
- Below the diagonal: Toolchains.NativeAot uses a module listed above it, which is the healthy direction.
39→29 Toolchains.NativeAot uses Toolchains.DotNetCli✕
- Connections
- 1 pair of types, where a type in Toolchains.NativeAot uses a type in Toolchains.DotNetCli.
- The types involved
BenchmarkDotNet.Toolchains.NativeAot.NativeAotSettings→BenchmarkDotNet.Toolchains.DotNetCli.DotNetCliSettings
- Direction
- Toolchains.NativeAot uses Toolchains.DotNetCli, so a change to Toolchains.DotNetCli can break Toolchains.NativeAot, while a change to Toolchains.NativeAot can't break Toolchains.DotNetCli.
- Position
- Below the diagonal: Toolchains.NativeAot uses a module listed above it, which is the healthy direction.
39→33 Toolchains.NativeAot uses Toolchains.CsProj✕
- Connections
- 2 pairs of types, where a type in Toolchains.NativeAot uses a type in Toolchains.CsProj.
- The types involved
BenchmarkDotNet.Toolchains.NativeAot.CsProjNativeAotBuilder→BenchmarkDotNet.Toolchains.CsProj.CsProjBuilderBenchmarkDotNet.Toolchains.NativeAot.CsProjNativeAotToolchain→BenchmarkDotNet.Toolchains.CsProj.CsProjNetToolchain
- Direction
- Toolchains.NativeAot uses Toolchains.CsProj, so a change to Toolchains.CsProj can break Toolchains.NativeAot, while a change to Toolchains.NativeAot can't break Toolchains.CsProj.
- Position
- Below the diagonal: Toolchains.NativeAot uses a module listed above it, which is the healthy direction.
40→2 Toolchains.Wasm uses Characteristics✕
- Connections
- 2 pairs of types, where a type in Toolchains.Wasm uses a type in Characteristics.
- The types involved
BenchmarkDotNet.Toolchains.Wasm.CsProjWasmToolchain→BenchmarkDotNet.Characteristics.IResolverBenchmarkDotNet.Toolchains.Wasm.WasmExecutor→BenchmarkDotNet.Characteristics.IResolver
- Direction
- Toolchains.Wasm uses Characteristics, so a change to Characteristics can break Toolchains.Wasm, while a change to Toolchains.Wasm can't break Characteristics.
- Position
- Below the diagonal: Toolchains.Wasm uses a module listed above it, which is the healthy direction.
40→5 Toolchains.Wasm uses Toolchains.Results✕
- Connections
- 1 pair of types, where a type in Toolchains.Wasm uses a type in Toolchains.Results.
- The types involved
BenchmarkDotNet.Toolchains.Wasm.WasmExecutor→BenchmarkDotNet.Toolchains.Results.ExecuteResult
- Direction
- Toolchains.Wasm uses Toolchains.Results, so a change to Toolchains.Results can break Toolchains.Wasm, while a change to Toolchains.Wasm can't break Toolchains.Results.
- Position
- Below the diagonal: Toolchains.Wasm uses a module listed above it, which is the healthy direction.
40→7 Toolchains.Wasm uses Toolchains.Parameters✕
- Connections
- 1 pair of types, where a type in Toolchains.Wasm uses a type in Toolchains.Parameters.
- The types involved
BenchmarkDotNet.Toolchains.Wasm.WasmExecutor→BenchmarkDotNet.Toolchains.Parameters.ExecuteParameters
- Direction
- Toolchains.Wasm uses Toolchains.Parameters, so a change to Toolchains.Parameters can break Toolchains.Wasm, while a change to Toolchains.Wasm can't break Toolchains.Parameters.
- Position
- Below the diagonal: Toolchains.Wasm uses a module listed above it, which is the healthy direction.
40→8 Toolchains.Wasm uses ConsoleArguments✕
- Connections
- 1 pair of types, where a type in Toolchains.Wasm uses a type in ConsoleArguments.
- The types involved
BenchmarkDotNet.Toolchains.Wasm.WasmSettings→BenchmarkDotNet.ConsoleArguments.CommandLineOptions
- Direction
- Toolchains.Wasm uses ConsoleArguments, so a change to ConsoleArguments can break Toolchains.Wasm, while a change to Toolchains.Wasm can't break ConsoleArguments.
- Position
- Below the diagonal: Toolchains.Wasm uses a module listed above it, which is the healthy direction.
40→9 Toolchains.Wasm uses Toolchains✕
- Connections
- 4 pairs of types, where a type in Toolchains.Wasm uses a type in Toolchains.
- The types involved
BenchmarkDotNet.Toolchains.Wasm.CsProjWasmBuilder→BenchmarkDotNet.Toolchains.ArtifactsPathsBenchmarkDotNet.Toolchains.Wasm.WasmExecutor→BenchmarkDotNet.Toolchains.ArtifactsPathsBenchmarkDotNet.Toolchains.Wasm.WasmExecutor→BenchmarkDotNet.Toolchains.IExecutorBenchmarkDotNet.Toolchains.Wasm.WasmSettings→BenchmarkDotNet.Toolchains.ArtifactsPaths
- Direction
- Toolchains.Wasm uses Toolchains, so a change to Toolchains can break Toolchains.Wasm, while a change to Toolchains.Wasm can't break Toolchains.
- Position
- Below the diagonal: Toolchains.Wasm uses a module listed above it, which is the healthy direction.
40→10 Toolchains.Wasm uses Running✕
- Connections
- 4 pairs of types, where a type in Toolchains.Wasm uses a type in Running.
- The types involved
BenchmarkDotNet.Toolchains.Wasm.CsProjWasmBuilder→BenchmarkDotNet.Running.BuildPartitionBenchmarkDotNet.Toolchains.Wasm.CsProjWasmToolchain→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Toolchains.Wasm.WasmExecutor→BenchmarkDotNet.Running.BenchmarkCaseBenchmarkDotNet.Toolchains.Wasm.WasmExecutor→BenchmarkDotNet.Running.BenchmarkId
- Direction
- Toolchains.Wasm uses Running, so a change to Running can break Toolchains.Wasm, while a change to Toolchains.Wasm can't break Running.
- Position
- Below the diagonal: Toolchains.Wasm uses a module listed above it, which is the healthy direction.
40→11 Toolchains.Wasm uses Validators✕
- Connections
- 1 pair of types, where a type in Toolchains.Wasm uses a type in Validators.
- The types involved
BenchmarkDotNet.Toolchains.Wasm.CsProjWasmToolchain→BenchmarkDotNet.Validators.ValidationError
- Direction
- Toolchains.Wasm uses Validators, so a change to Validators can break Toolchains.Wasm, while a change to Toolchains.Wasm can't break Validators.
- Position
- Below the diagonal: Toolchains.Wasm uses a module listed above it, which is the healthy direction.
40→15 Toolchains.Wasm uses Environments✕
- Connections
- 4 pairs of types, where a type in Toolchains.Wasm uses a type in Environments.
- The types involved
BenchmarkDotNet.Toolchains.Wasm.CsProjCoreWasmToolchain→BenchmarkDotNet.Environments.CoreWasmRuntimeBenchmarkDotNet.Toolchains.Wasm.CsProjMonoWasmAotToolchain→BenchmarkDotNet.Environments.MonoWasmAotRuntimeBenchmarkDotNet.Toolchains.Wasm.CsProjMonoWasmToolchain→BenchmarkDotNet.Environments.MonoWasmRuntimeBenchmarkDotNet.Toolchains.Wasm.CsProjWasmToolchain→BenchmarkDotNet.Environments.WasmRuntime
- Direction
- Toolchains.Wasm uses Environments, so a change to Environments can break Toolchains.Wasm, while a change to Toolchains.Wasm can't break Environments.
- Position
- Below the diagonal: Toolchains.Wasm uses a module listed above it, which is the healthy direction.
40→18 Toolchains.Wasm uses Engines✕
- Connections
- 2 pairs of types, where a type in Toolchains.Wasm uses a type in Engines.
- The types involved
BenchmarkDotNet.Toolchains.Wasm.ProcessListener→BenchmarkDotNet.Engines.IpcListenerBenchmarkDotNet.Toolchains.Wasm.WasmExecutor→BenchmarkDotNet.Engines.IpcListener
- Direction
- Toolchains.Wasm uses Engines, so a change to Engines can break Toolchains.Wasm, while a change to Toolchains.Wasm can't break Engines.
- Position
- Below the diagonal: Toolchains.Wasm uses a module listed above it, which is the healthy direction.
40→25 Toolchains.Wasm uses Diagnosers✕
- Connections
- 3 pairs of types, where a type in Toolchains.Wasm uses a type in Diagnosers.
- The types involved
BenchmarkDotNet.Toolchains.Wasm.WasmExecutor→BenchmarkDotNet.Diagnosers.CompositeInProcessDiagnoserBenchmarkDotNet.Toolchains.Wasm.WasmExecutor→BenchmarkDotNet.Diagnosers.IDiagnoserBenchmarkDotNet.Toolchains.Wasm.WasmExecutor→BenchmarkDotNet.Diagnosers.RunMode
- Direction
- Toolchains.Wasm uses Diagnosers, so a change to Diagnosers can break Toolchains.Wasm, while a change to Toolchains.Wasm can't break Diagnosers.
- Position
- Below the diagonal: Toolchains.Wasm uses a module listed above it, which is the healthy direction.
40→27 Toolchains.Wasm uses Loggers✕
- Connections
- 3 pairs of types, where a type in Toolchains.Wasm uses a type in Loggers.
- The types involved
BenchmarkDotNet.Toolchains.Wasm.CsProjWasmBuilder→BenchmarkDotNet.Loggers.ILoggerBenchmarkDotNet.Toolchains.Wasm.WasmExecutor→BenchmarkDotNet.Loggers.AsyncProcessOutputReaderBenchmarkDotNet.Toolchains.Wasm.WasmExecutor→BenchmarkDotNet.Loggers.ILogger
- Direction
- Toolchains.Wasm uses Loggers, so a change to Loggers can break Toolchains.Wasm, while a change to Toolchains.Wasm can't break Loggers.
- Position
- Below the diagonal: Toolchains.Wasm uses a module listed above it, which is the healthy direction.
40→29 Toolchains.Wasm uses Toolchains.DotNetCli✕
- Connections
- 1 pair of types, where a type in Toolchains.Wasm uses a type in Toolchains.DotNetCli.
- The types involved
BenchmarkDotNet.Toolchains.Wasm.WasmSettings→BenchmarkDotNet.Toolchains.DotNetCli.DotNetCliSettings
- Direction
- Toolchains.Wasm uses Toolchains.DotNetCli, so a change to Toolchains.DotNetCli can break Toolchains.Wasm, while a change to Toolchains.Wasm can't break Toolchains.DotNetCli.
- Position
- Below the diagonal: Toolchains.Wasm uses a module listed above it, which is the healthy direction.
40→33 Toolchains.Wasm uses Toolchains.CsProj✕
- Connections
- 2 pairs of types, where a type in Toolchains.Wasm uses a type in Toolchains.CsProj.
- The types involved
BenchmarkDotNet.Toolchains.Wasm.CsProjWasmBuilder→BenchmarkDotNet.Toolchains.CsProj.CsProjBuilderBenchmarkDotNet.Toolchains.Wasm.CsProjWasmToolchain→BenchmarkDotNet.Toolchains.CsProj.CsProjNetToolchain
- Direction
- Toolchains.Wasm uses Toolchains.CsProj, so a change to Toolchains.CsProj can break Toolchains.Wasm, while a change to Toolchains.Wasm can't break Toolchains.CsProj.
- Position
- Below the diagonal: Toolchains.Wasm uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 81 | High / Critical |
| A07:2025 — Authentication Failures | 13 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 13 | Medium |
Roadmap
Top priorities: Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.); Resolve the 11 REDACTED finding(s) in Secrets (history) — start with REDACTED (11); Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.). | +12.2 pts | Medium | Data Protection |
| Resolve the 11 REDACTED finding(s) in Secrets (history) — start with REDACTED (11). | +6.9 pts | Medium | Secrets (history) |
| Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. | +1.8 pts | Low | Static Analysis (SAST) |
| Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2). | +1.8 pts | Low | Static Analysis (SAST) |
| Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. | +1.6 pts | Low | Secrets (history) |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +1.3 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +1.3 pts | Low | Supply-chain Provenance & Signing |
| Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (`System.IO.Hashing.XxHash64`/`Crc32`) where it only derives an identifier such as a cache key or a mutex name. This repository constructs a collision-broken hash (MD5/SHA1) at 2 sites, not one: `samples/BenchmarkDotNet.Samples/IntroFluentConfigBuilder.cs:16` (MD5), `samples/BenchmarkDotNet.Samples/IntroStatisticsColumns.cs:12` (MD5). Each is a separate decision — fixing only the line this row cites leaves the others in place. | +1.4 pts | Medium | Cryptographic Hygiene |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Secrets (history): REDACTED: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| src/BenchmarkDotNet/Environments/PhysicalMemoryInfo.cs | 2.7 | Slop | Explicit Debt: EmptyCatchBlock |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| tests/BenchmarkDotNet.Tests/ParamsSourceTests.cs | 3.4 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 3.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| tests/BenchmarkDotNet.Tests/Validators/ParamsValidatorTests.cs | 4.0 | Mixed | Explicit Debt: FileScopedPragmaDisable |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/BenchmarkDotNet/Engines/Consumer.cs | 5.2 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| tests/BenchmarkDotNet.Tests/Validators/SourceReturnTypeValidatorTests.cs | 5.4 | Mixed | Explicit Debt: FileScopedPragmaDisable |
| tests/BenchmarkDotNet.Tests/BenchmarkDotNet.Tests.csproj | 5.4 | Mixed | Explicit Debt: NoWarnInCsproj |
| src/BenchmarkDotNet/Engines/Engine.cs | 5.5 | Mixed | Cyclomatic Complexity: Engine.RunCore (cyclomatic 19) |
| src/BenchmarkDotNet/BenchmarkDotNet.csproj | 5.6 | Mixed | Explicit Debt: NoWarnInCsproj — 9 warning codes suppressed in one element |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 66 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 66 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 786 of 804 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
- D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 1,458 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 9 test source file(s) (.vb, .fs) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- 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 scored — the test tier(s) ran but surfaced none of this repository's 2577 test method(s) to the runner, so flakiness couldn't be exercised. This is an analysis-environment limitation, not a finding about the tests.
- 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. The NuGet registry this repository's packages resolve from could not be reached on this run, so no outdated, vulnerable or deprecated package could be read. The tool said: Unable to load the service index for source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet6/nuget/v3/index.json. The proxy tunnel request to proxy 'http://egress:3128/' failed with status code '403'.. This is OUR side and an ENVIRONMENT fault — the collector exists and ran — so the remedy is the scan's network path to pkgs.dev.azure.com, and a re-run with it reachable measures 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: Cannot open project 'samples/BenchmarkDotNet.Samples.FSharp/BenchmarkDotNet.Samples.FSharp.fsproj' because the file extension '.fsproj' is not associated with a language.
- D18 Solution Shape — 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 build did not finish within its budget on this run; structural metrics are reported, build/warning status is unknown.
- 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.
- 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.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — 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 (60,541 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 — 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 source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — 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. Pkgs.dev.azure.com could not be reached (NU1301: Unable to load the service index for source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet6/nuget/v3/index.json. The proxy tunnel request to proxy 'http://egress:3128/' failed with status code '403'.). 2 of 3 declared ecosystem(s) (npm,osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/BenchmarkDotNet.Annotations/Attributes/AsyncCallerTypeAttribute.cs`, `src/BenchmarkDotNet.Annotations/Attributes/GenericTypeArgumentsAttribute.cs`, `src/BenchmarkDotNet.CodeFixers/ArgumentsSourceElementTypeCodeFixProvider.cs`, `src/BenchmarkDotNet.Diagnostics.dotMemory/DotMemoryDiagnoser.cs`, `src/BenchmarkDotNet.Diagnostics.dotTrace/DotTraceDiagnoser.cs`, … (+74 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.
- 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: a native UI project (samples/BenchmarkDotNet.Samples.Maui/App.xaml). 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 — 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. 26 further occurrence(s) are not listed individually; the score already reflects all 66.
- 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.
- Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for tests/BenchmarkDotNet.Analyzers.Tests/BenchmarkDotNet.Analyzers.Tests.csproj, tests/BenchmarkDotNet.Exporters.Plotting.Tests/BenchmarkDotNet.Exporters.Plotting.Tests.csproj, samples/BenchmarkDotNet.Samples.Maui/BenchmarkDotNet.Samples.Maui.csproj, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- 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.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- 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.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
44 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was BenchmarkClassAnalyzer.AnalyzeClassDeclaration at 98. A further 6 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being SourceCodeHelper.ToSourceCode at 19 — they are counted neither in the figure above nor in this dimension's score. 4 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/BenchmarkDotNet/Environments/Runtimes/CoreRuntime.cs (CoreRuntime.From at 18), src/BenchmarkDotNet/Helpers/Reflection.Emit/IlGeneratorDefaultValueExtensions.cs (IlGeneratorDefaultValueExtensions.EmitLoadDefaultPrimitive at 17), src/BenchmarkDotNet/Toolchains/NetCoreApp/CsProjCoreToolchain.cs (CsProjCoreToolchain.From at 17), src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncStateMachineEmitter.cs (RunnableEmitter.BeginAsyncStateMachineTypeBuilder at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with BenchmarkClassAnalyzer.AnalyzeClassDeclaration (cyclomatic 98). — Refactoring it lifts Cyclomatic Complexity from 6.0 to about 6.5/10.
D2 · Cognitive Complexity
79 method(s) exceeded the cognitive complexity threshold of 15; the worst was BenchmarkClassAnalyzer.AnalyzeClassDeclaration at 499.
What to do
- Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with BenchmarkClassAnalyzer.AnalyzeClassDeclaration (cognitive 499). — Refactoring it lifts Cognitive Complexity from 4.3 to about 5.8/10.
D3 · God Classes
14 god class(es) detected.
What to do
- Resolve the 5 MethodTooLong finding(s) in God Classes — start with AsyncEnumerableCoreEmitter.cs, AsyncCoreEmitter.cs, BenchmarkClassAnalyzer.cs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 TooManyMethods finding(s) in God Classes — start with ManualConfig.cs, RunnableEmitter.cs, CharacteristicObject.cs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 ClassTooLong finding(s) in God Classes — start with BenchmarkRunnerClean.cs, ConfigParser.cs, AsyncEnumerableCoreEmitter.cs. — One of this dimension's main actionable groups (3 warning-level).
D4 · Code Duplication
64 duplicated block group(s) detected. A further 31 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 5 of the 95 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 5 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with GeneralParameterAttributesAnalyzer.cs, AnalyzerHelper.cs, CompositeResolver.cs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with SetupCleanupAsyncEnumerableAnalyzer.cs, InProcessEmitRunner.cs, InliningDiagnoser.cs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with DotNetCliExecutor.cs, BenchmarkCancellationAttributeAnalyzer.cs, Arm64Disassembler.cs. — One of this dimension's main actionable groups (4 warning-level).
D5 · Coupling
57 projects, 0 dependency cycle(s), 3 unstable depended-on project(s).
What to do
- Resolve the 1 Unstable project BenchmarkDotNet.CodeFixers finding(s) in Coupling — start with BenchmarkDotNet.CodeFixers.csproj. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Unstable project BenchmarkDotNet.Diagnostics.Windows finding(s) in Coupling — start with BenchmarkDotNet.Diagnostics.Windows.csproj. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Unstable project BenchmarkDotNet.Exporters.Plotting finding(s) in Coupling — start with BenchmarkDotNet.Exporters.Plotting.csproj. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 185 classes have LCOM4 above 3.
D10 · Test Quality
8 skipped (8 with a documented reason), 3 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1458 tests. Measured on the C# suite only — at least 9 test source file(s) (.vb, .fs) went unread, so its test quality is unmeasured and is not in these counts.
What to do
- Resolve the 3 No assertions finding(s) in Test Quality — start with ParamsSourceTests.cs, EnvRequirementCheckerTests.cs, RuntimeAsyncEmitTest.cs. — One of this dimension's main actionable groups (3 warning-level).
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 278 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 54 direct `PackageReference`(s), and 200 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
Top hotspots: src/BenchmarkDotNet/ConsoleArguments/ConfigParser.cs (8×31=248); src/BenchmarkDotNet.Analyzers/Attributes/ArgumentsAttributeAnalyzer.cs (3×59=177); src/BenchmarkDotNet/Running/BenchmarkRunnerClean.cs (9×19=171)
What to do
- Resolve the 7 Hotspot finding(s) in Churn × Complexity Hotspots — start with ConfigParser.cs, ArgumentsAttributeAnalyzer.cs, BenchmarkRunnerClean.cs. — One of this dimension's main actionable groups (7 warning-level).
D16 · Bus Factor
No source file's living knowledge is concentrated in a single author.
D17 · Explicit Debt
264 deducted debt markers + unmeasured dead symbols across 60541 LoC in the .NET projects (2.0/KLoC) → score 5.9. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
What to do
- Resolve the 22 NoWarnInCsproj finding(s) in Explicit Debt — start with BenchmarkDotNet.Tests.csproj (5), BenchmarkDotNet.Weaver.csproj (3), BenchmarkDotNet.IntegrationTests.csproj (2). — One of this dimension's main actionable groups (22 issue-level).
- Resolve the 18 EmptyCatchBlock finding(s) in Explicit Debt — start with PhysicalMemoryInfo.cs (4), ProcessCleanupHelper.cs (3), IntroExceptionDiagnoser.cs. — One of this dimension's main actionable groups (18 issue-level).
- Resolve the 13 WriteOnlyPrivateField finding(s) in Explicit Debt — start with Consumer.cs (12), ParamsSourceTests.cs. — One of this dimension's main actionable groups (13 issue-level).
D18 · Solution Shape
57 projects, 4227 source files, 103654 hand-written lines of code (60541 production / 43113 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 1175 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 93 inter-project edges (build status unknown — did not finish). Measured across 2 solutions loaded as one workspace: `BenchmarkDotNet.slnx`, `samples/BenchmarkDotNet.Maui.slnx`.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 45 document(s) read across 10 unit(s).
D24 · Comment Value
22 of 1923 judged comments only repeat the code they sit on (1.1 %). 156 comment(s) in another language or script were not judged.
What to do
- Resolve the 22 redundant comment finding(s) in Comment Value — start with AsyncBenchmarkCodeFixProvider.cs (4), RunningEmptyBenchmarkTests.cs (3), DisassemblyDiagnoserTests.cs (2). — One of this dimension's main actionable groups (22 recommendation-level).
D26 · Project Cohesion
1 of 31 projects flagged as possibly oversized/incoherent.
D27 · Navigability
84 % of calls cross a namespace and 1 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.
D28 · Secrets (history)
12 finding(s): 0 critical, 12 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 11 REDACTED finding(s) in Secrets (history) — start with REDACTED (11). — One of this dimension's main actionable groups (11 issue-level).
- Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
82 finding(s): 0 critical, 82 high, 0 medium, 0 low. 64 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 82 file(s) — `docs/logo/logo-cmyk.eps`, `docs/logo/logo-rgb.eps`, `src/BenchmarkDotNet.Annotations/Attributes/AsyncCallerTypeAttribute.cs` (line 7), `src/BenchmarkDotNet.Annotations/Attributes/GenericTypeArgumentsAttribute.cs` (lines 11–13), `src/BenchmarkDotNet.CodeFixers/ArgumentsSourceElementTypeCodeFixProvider.cs` (lines 491–492, lines 509–565), … (+77 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 65 of those file(s) — `src/BenchmarkDotNet.Annotations/Attributes/AsyncCallerTypeAttribute.cs`, `src/BenchmarkDotNet.CodeFixers/ArgumentsSourceElementTypeCodeFixProvider.cs`, `src/BenchmarkDotNet.Diagnostics.dotMemory/DotMemoryDiagnoser.cs`, `src/BenchmarkDotNet.Diagnostics.dotTrace/DotTraceDiagnoser.cs`, `src/BenchmarkDotNet/Attributes/Columns/StdErrorColumnAttribute.cs`, … (+60 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. In 6 of those file(s) — `src/BenchmarkDotNet/Attributes/Exporters/PerfonarExporterAttribute.cs`, `src/BenchmarkDotNet/Code/DeclarationsProvider.cs`, `src/BenchmarkDotNet/Detectors/Cpu/HardwareIntrinsics.cs`, `src/BenchmarkDotNet/Detectors/Cpu/Windows/WindowsCpuDetector.cs`, `src/BenchmarkDotNet/Detectors/OsDetector.cs`, … (+1 more) — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. Separately, one or more rules could not re-parse an embedded snippet in 8 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- No action in Static Analysis (SAST) — all 64 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 (64 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in the 2 ecosystem(s) that were scanned (npm,osv). Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,osv), and the findings above are real and complete for them. nuget was not scanned (nuget: pkgs.dev.azure.com could not be reached (NU1301: Unable to load the service index for source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet6/nuget/v3/index.json. The proxy tunnel request to proxy 'http://egress:3128/' failed with status code '403'.)), so this is not the whole dependency surface and the result is reported at reduced confidence.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked.
D35 · Change Coupling
Strongest change-coupling: InProcessEmitExecutor.cs↔InProcessNoEmitExecutor.cs 91%; RuntimeMoniker.cs↔ConfigParser.cs 90%; RuntimeMoniker.cs↔DotTraceDiagnoser.cs 82%
What to do
- Resolve the 3 Boundary-crossing change coupling finding(s) in Change Coupling — start with RuntimeMoniker.cs (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 5 Change coupling finding(s) in Change Coupling — start with Engine.cs (2), InProcessEmitExecutor.cs, DotNetCliExecutor.cs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with WasmRuntime.cs. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 33 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons
- `EventPipeProfiler` keeps one instance of itself in the static `Default`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (session, benchmarkToTraceFile, collectingTask; e.g. `session` at line 82). — src/BenchmarkDotNet/Diagnosers/EventPipeProfiler.cs:17
- `ExceptionDiagnoser` keeps one instance of itself in the static `Default`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (results; e.g. `results` at line 51). — src/BenchmarkDotNet/Diagnosers/ExceptionDiagnoser.cs:18
- `PerfCollectProfiler` keeps one instance of itself in the static `Default`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (perfCollectFile, perfCollectProcess, benchmarkToTraceFile, cliPathWithSymbolsInstalled; e.g. `perfCollectFile` at line 94). — REDACTED:24
- `ThreadingDiagnoser` keeps one instance of itself in the static `Default`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (results; e.g. `results` at line 71). — src/BenchmarkDotNet/Diagnosers/ThreadingDiagnoser.cs:17
- `ConsoleLogger` keeps one instance of itself in the static `Default`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (colorScheme; e.g. `colorScheme` at line 95). — src/BenchmarkDotNet/Loggers/ConsoleLogger.cs:9
- `DefaultConfig` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (customDefaultConfig; e.g. `customDefaultConfig` at line 35). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/BenchmarkDotNet/Configs/DefaultConfig.cs:19
- `HostEnvironmentInfo` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (current; e.g. `current` at line 85). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/BenchmarkDotNet/Environments/HostEnvironmentInfo.cs:22
- `PathFeatures` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (s_onCore, s_osEnabled; e.g. `s_onCore` at line 74). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/BenchmarkDotNet/Extensions/PathFeatures.cs:12
- `UserInteraction` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (consoleCancelKeyPressed; e.g. `consoleCancelKeyPressed` at line 14). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/BenchmarkDotNet/Running/UserInteraction.cs:10
- `JsHost` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (s_signalAckTaskSource; e.g. `s_signalAckTaskSource` at line 38). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/BenchmarkDotNet/Engines/JsHost.cs:13
- `MarkdownBuilder` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (allMilestones, AuthorNames; e.g. `allMilestones` at line 81). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — build/BenchmarkDotNet.Build/Runners/Changelog/ChangelogDetailsBuilder.cs:31
What to do
- Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
- A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
AX3 · Project dependency cycles
- The namespaces BenchmarkDotNet.Analysers ↔ BenchmarkDotNet.Attributes ↔ BenchmarkDotNet.Code ↔ BenchmarkDotNet.Columns ↔ BenchmarkDotNet.Configs ↔ BenchmarkDotNet.ConsoleArguments ↔ BenchmarkDotNet.ConsoleArguments.ListBenchmarks ↔ BenchmarkDotNet.Diagnosers ↔ BenchmarkDotNet.Disassemblers ↔ BenchmarkDotNet.Engines ↔ BenchmarkDotNet.Environments ↔ BenchmarkDotNet.EventProcessors ↔ BenchmarkDotNet.Exporters ↔ BenchmarkDotNet.Exporters.Csv ↔ BenchmarkDotNet.Extensions ↔ BenchmarkDotNet.Filters ↔ BenchmarkDotNet.Helpers ↔ BenchmarkDotNet.Jobs ↔ BenchmarkDotNet.Loggers ↔ BenchmarkDotNet.Mathematics ↔ BenchmarkDotNet.Models ↔ BenchmarkDotNet.Order ↔ BenchmarkDotNet.Parameters ↔ BenchmarkDotNet.Portability ↔ BenchmarkDotNet.Reports ↔ BenchmarkDotNet.Running ↔ BenchmarkDotNet.Toolchains ↔ BenchmarkDotNet.Toolchains.Parameters ↔ BenchmarkDotNet.Toolchains.Results ↔ BenchmarkDotNet.Validators depend on each other. The lightest dependency in the cycle is BenchmarkDotNet.Analysers → BenchmarkDotNet.Loggers (BenchmarkDotNet.Analysers.ConclusionHelper → BenchmarkDotNet.Loggers.ILogger, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/BenchmarkDotNet/Analysers/ConclusionHelper.cs:1
- The namespaces BenchmarkDotNet.Build ↔ BenchmarkDotNet.Build.Meta ↔ BenchmarkDotNet.Build.Options ↔ BenchmarkDotNet.Build.Runners ↔ BenchmarkDotNet.Build.Runners.Changelog depend on each other. The lightest dependency in the cycle is BenchmarkDotNet.Build → BenchmarkDotNet.Build.Meta (BenchmarkDotNet.Build.BuildContext → BenchmarkDotNet.Build.Meta.VersionHistory, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — build/BenchmarkDotNet.Build/BuildContext.cs:7
What to do
- Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
- `IConfig` declares 23 members: `GetColumnProviders`, `GetExporters`, `GetLoggers`, `GetDiagnosers`, `GetAnalysers`, `GetJobs`, `GetValidators`, `GetHardwareCounters`, `GetFilters`, `GetLogicalGroupRules`, `GetEventProcessors`, `GetColumnHidingRules`, `Orderer`, `CategoryDiscoverer`, `SummaryStyle`, `UnionRule`, `ArtifactsPath`, `Title`, `CultureInfo`, `Options`, `BuildTimeout`, `WakeLock`, `ConfigAnalysisConclusion`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/BenchmarkDotNet/Configs/IConfig.cs:17
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX8 · Test isolation
C1 · Data Protection
- No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
What to do
- Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
- Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
C4 · Data Retention
- A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob), a documented retention period / data-expiry.
What to do
- Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `Consume` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — src/BenchmarkDotNet/Engines/Engine.cs:263
- `SendSignalAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/BenchmarkDotNet/Engines/NoAcknowledgementConsoleHost.cs:33
- `SaveAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/BenchmarkDotNet/Extensions/XDocumentExtensions.cs:12
- 2 guards above `return false;` also return `false`, so no input can make them matter. Implement the distinction that was intended, or delete the guards. — src/BenchmarkDotNet/Helpers/SourceCodeHelper.cs:113
- Control only reaches here when `x.HasValue(characteristic)` is true, because the guard on line 58 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/BenchmarkDotNet/Jobs/JobComparer.cs:66
- `Read`'s body only throws NotSupportedException — sometimes a deliberate contract, often an unfinished stub. Confirm it's intentional. — src/BenchmarkDotNet/ConsoleArguments/ListBenchmarks/BenchmarkCaseJsonConverter.cs:57
- `GetHashCode`'s body only throws NotSupportedException — sometimes a deliberate contract, often an unfinished stub. Confirm it's intentional. — src/BenchmarkDotNet/Helpers/HashCode.cs:146
- `Equals`'s body only throws NotSupportedException — sometimes a deliberate contract, often an unfinished stub. Confirm it's intentional. — src/BenchmarkDotNet/Helpers/HashCode.cs:151
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×31) — src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:126, src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:132, src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:136, …
- 27 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). — src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:378
What to do
- Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Describe the projects a newcomer cannot place from the root README: 2 of 2 have no README of their own, in their folder or in their family's project (`src/BenchmarkDotNet.Weaver`, `build/BenchmarkDotNet.Build`).
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
- `BenchmarkDotNet.Diagnostics.Windows.ConcurrencyVisualizerProfiler` (src/BenchmarkDotNet.Diagnostics.Windows/ConcurrencyVisualizerProfiler.cs:23) is public, and the library's own code uses it, but no other project in this repository uses it (read: `BenchmarkDotNet.Exporters.Plotting.Tests(net472)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net10.0)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net472)`, `BenchmarkDotNet.Samples(net10.0)`, `BenchmarkDotNet.Samples(net472)`, `BenchmarkDotNet.Tests(net472)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/BenchmarkDotNet.Diagnostics.Windows/ConcurrencyVisualizerProfiler.cs:23
- `BenchmarkDotNet.Diagnostics.Windows.EtwProfiler` (src/BenchmarkDotNet.Diagnostics.Windows/EtwProfiler.cs:17) is public, and the library's own code uses it, but no other project in this repository uses it (read: `BenchmarkDotNet.Exporters.Plotting.Tests(net472)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net10.0)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net472)`, `BenchmarkDotNet.Samples(net10.0)`, `BenchmarkDotNet.Samples(net472)`, `BenchmarkDotNet.Tests(net472)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/BenchmarkDotNet.Diagnostics.Windows/EtwProfiler.cs:17
- `BenchmarkDotNet.Diagnostics.Windows.HardwareCounters` (src/BenchmarkDotNet.Diagnostics.Windows/HardwareCounters.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `BenchmarkDotNet.Exporters.Plotting.Tests(net472)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net10.0)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net472)`, `BenchmarkDotNet.Samples(net10.0)`, `BenchmarkDotNet.Samples(net472)`, `BenchmarkDotNet.Tests(net472)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/BenchmarkDotNet.Diagnostics.Windows/HardwareCounters.cs:9
- `BenchmarkDotNet.Diagnostics.Windows.InliningDiagnoser` (src/BenchmarkDotNet.Diagnostics.Windows/InliningDiagnoser.cs:8) is public, and the library's own code uses it, but no other project in this repository uses it (read: `BenchmarkDotNet.Exporters.Plotting.Tests(net472)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net10.0)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net472)`, `BenchmarkDotNet.Samples(net10.0)`, `BenchmarkDotNet.Samples(net472)`, `BenchmarkDotNet.Tests(net472)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/BenchmarkDotNet.Diagnostics.Windows/InliningDiagnoser.cs:8
- `BenchmarkDotNet.Diagnostics.Windows.JitStatsDiagnoser` (src/BenchmarkDotNet.Diagnostics.Windows/JitStatsDiagnoser.cs:11) is public, and the library's own code uses it, but no other project in this repository uses it (read: `BenchmarkDotNet.Exporters.Plotting.Tests(net472)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net10.0)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net472)`, `BenchmarkDotNet.Samples(net10.0)`, `BenchmarkDotNet.Samples(net472)`, `BenchmarkDotNet.Tests(net472)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/BenchmarkDotNet.Diagnostics.Windows/JitStatsDiagnoser.cs:11
- `BenchmarkDotNet.Diagnostics.Windows.NativeMemoryProfiler` (src/BenchmarkDotNet.Diagnostics.Windows/NativeMemoryProfiler.cs:15) is public, and the library's own code uses it, but no other project in this repository uses it (read: `BenchmarkDotNet.Exporters.Plotting.Tests(net472)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net10.0)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net472)`, `BenchmarkDotNet.Samples(net10.0)`, `BenchmarkDotNet.Samples(net472)`, `BenchmarkDotNet.Tests(net472)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/BenchmarkDotNet.Diagnostics.Windows/NativeMemoryProfiler.cs:15
- `BenchmarkDotNet.Diagnostics.Windows.TailCallDiagnoser` (src/BenchmarkDotNet.Diagnostics.Windows/TailCallDiagnoser.cs:12) is public, and the library's own code uses it, but no other project in this repository uses it (read: `BenchmarkDotNet.Exporters.Plotting.Tests(net472)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net10.0)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net472)`, `BenchmarkDotNet.Samples(net10.0)`, `BenchmarkDotNet.Samples(net472)`, `BenchmarkDotNet.Tests(net472)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/BenchmarkDotNet.Diagnostics.Windows/TailCallDiagnoser.cs:12
- `BenchmarkDotNet.Diagnostics.Windows.Tracing.EngineEventLogParser` (src/BenchmarkDotNet.Diagnostics.Windows/Tracing/EngineEventLogParser.cs:8) is public, and the library's own code uses it, but no other project in this repository uses it (read: `BenchmarkDotNet.Exporters.Plotting.Tests(net472)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net10.0)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net472)`, `BenchmarkDotNet.Samples(net10.0)`, `BenchmarkDotNet.Samples(net472)`, `BenchmarkDotNet.Tests(net472)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/BenchmarkDotNet.Diagnostics.Windows/Tracing/EngineEventLogParser.cs:8
- `BenchmarkDotNet.Diagnostics.Windows.Tracing.NativeMemoryLogParser` (src/BenchmarkDotNet.Diagnostics.Windows/Tracing/NativeMemoryLogParser.cs:17) is public, and the library's own code uses it, but no other project in this repository uses it (read: `BenchmarkDotNet.Exporters.Plotting.Tests(net472)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net10.0)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net472)`, `BenchmarkDotNet.Samples(net10.0)`, `BenchmarkDotNet.Samples(net472)`, `BenchmarkDotNet.Tests(net472)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/BenchmarkDotNet.Diagnostics.Windows/Tracing/NativeMemoryLogParser.cs:17
- `BenchmarkDotNet.Diagnostics.Windows.Tracing.TraceLogParser` (src/BenchmarkDotNet.Diagnostics.Windows/Tracing/TraceLogParser.cs:11) is public, and the library's own code uses it, but no other project in this repository uses it (read: `BenchmarkDotNet.Exporters.Plotting.Tests(net472)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net10.0)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net472)`, `BenchmarkDotNet.Samples(net10.0)`, `BenchmarkDotNet.Samples(net472)`, `BenchmarkDotNet.Tests(net472)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/BenchmarkDotNet.Diagnostics.Windows/Tracing/TraceLogParser.cs:11
- `BenchmarkDotNet.Diagnostics.Windows.Tracing.ProcessMetrics` (src/BenchmarkDotNet.Diagnostics.Windows/Tracing/TraceLogParser.cs:91) is public, and the library's own code uses it, but no other project in this repository uses it (read: `BenchmarkDotNet.Exporters.Plotting.Tests(net472)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net10.0)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net472)`, `BenchmarkDotNet.Samples(net10.0)`, `BenchmarkDotNet.Samples(net472)`, `BenchmarkDotNet.Tests(net472)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/BenchmarkDotNet.Diagnostics.Windows/Tracing/TraceLogParser.cs:91
- `BenchmarkDotNet.Diagnostics.Windows.Tracing.IterationData` (src/BenchmarkDotNet.Diagnostics.Windows/Tracing/TraceLogParser.cs:218) is public, and the library's own code uses it, but no other project in this repository uses it (read: `BenchmarkDotNet.Exporters.Plotting.Tests(net472)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net10.0)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net472)`, `BenchmarkDotNet.Samples(net10.0)`, `BenchmarkDotNet.Samples(net472)`, `BenchmarkDotNet.Tests(net472)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/BenchmarkDotNet.Diagnostics.Windows/Tracing/TraceLogParser.cs:218
- `BenchmarkDotNet.Analysers.BaselineCustomAnalyzer` (src/BenchmarkDotNet/Analysers/BaselineCustomAnalyzer.cs:7) is public, and the library's own code uses it, but no other project in this repository uses it (read: `BenchmarkDotNet.Analyzers.Tests(net472)`, `BenchmarkDotNet.Diagnostics.Windows`, `BenchmarkDotNet.Diagnostics.dotMemory(net462)`, `BenchmarkDotNet.Diagnostics.dotMemory(netcoreapp3.1)`, `BenchmarkDotNet.Diagnostics.dotTrace(net462)`, `BenchmarkDotNet.Diagnostics.dotTrace(netcoreapp3.1)`, `BenchmarkDotNet.Exporters.Plotting`, `BenchmarkDotNet.Exporters.Plotting.Tests(net472)`, `BenchmarkDotNet.IntegrationTests.ConfigPerAssembly(net472)`, `BenchmarkDotNet.IntegrationTests.CustomPaths`, `BenchmarkDotNet.IntegrationTests.DisabledOptimizations(net472)`, `BenchmarkDotNet.IntegrationTests.EnabledOptimizations(net472)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net472)`, `BenchmarkDotNet.IntegrationTests.ManualRunning.MultipleFrameworks(net462)`, `BenchmarkDotNet.IntegrationTests.ManualRunning.MultipleFrameworks(net48)`, `BenchmarkDotNet.IntegrationTests.MonoBenchmarks(net472)`, `BenchmarkDotNet.IntegrationTests.SharedDiagnosers`, `BenchmarkDotNet.IntegrationTests.Static(net472)`, `BenchmarkDotNet.IntegrationTests.VisualBasic(net472)`, `BenchmarkDotNet.IntegrationTests.WasmBenchmarks(net472)`, `BenchmarkDotNet.Samples(net472)`, `BenchmarkDotNet.TestAdapter(net462)`, `BenchmarkDotNet.TestAdapter(netstandard2.0)`, `BenchmarkDotNet.Tests(net472)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/BenchmarkDotNet/Analysers/BaselineCustomAnalyzer.cs:7
- `BenchmarkDotNet.Analysers.BaselineCustomAnalyzer` (src/BenchmarkDotNet/Analysers/BaselineCustomAnalyzer.cs:7) is public, and the library's own code uses it, but no other project in this repository uses it (read: `BenchmarkDotNet.IntegrationTests.ManualRunning.MultipleFrameworks(net8.0)`, `BenchmarkDotNet.IntegrationTests.MonoBenchmarks(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/BenchmarkDotNet/Analysers/BaselineCustomAnalyzer.cs:7
- `BenchmarkDotNet.Analysers.BaselineCustomAnalyzer` (src/BenchmarkDotNet/Analysers/BaselineCustomAnalyzer.cs:7) is public, and the library's own code uses it, but no other project in this repository uses it (read: `BenchmarkDotNet.Analyzers.Tests(net10.0)`, `BenchmarkDotNet.Diagnostics.dotMemory(net10.0)`, `BenchmarkDotNet.Diagnostics.dotTrace(net10.0)`, `BenchmarkDotNet.Exporters.Plotting.Tests(net10.0)`, `BenchmarkDotNet.IntegrationTests`, `BenchmarkDotNet.IntegrationTests.ConfigPerAssembly(net10.0)`, `BenchmarkDotNet.IntegrationTests.DisabledOptimizations(net10.0)`, `BenchmarkDotNet.IntegrationTests.EnabledOptimizations(net10.0)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net10.0)`, `BenchmarkDotNet.IntegrationTests.ManualRunning.MultipleFrameworks(net10.0)`, `BenchmarkDotNet.IntegrationTests.Static(net10.0)`, `BenchmarkDotNet.IntegrationTests.VisualBasic(net10.0)`, `BenchmarkDotNet.IntegrationTests.WasmBenchmarks(net10.0)`, `BenchmarkDotNet.Samples(net10.0)`, `BenchmarkDotNet.Samples.Maui(net10.0-android)`, `BenchmarkDotNet.Samples.Maui(net10.0-ios)`, `BenchmarkDotNet.Samples.Maui(net10.0-maccatalyst)`, `BenchmarkDotNet.Tests(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/BenchmarkDotNet/Analysers/BaselineCustomAnalyzer.cs:7
- `BenchmarkDotNet.Analysers.CompositeAnalyser` (src/BenchmarkDotNet/Analysers/CompositeAnalyser.cs:6) is public, and the library's own code uses it, but no other project in this repository uses it (read: `BenchmarkDotNet.Analyzers.Tests(net472)`, `BenchmarkDotNet.Diagnostics.Windows`, `BenchmarkDotNet.Diagnostics.dotMemory(net462)`, `BenchmarkDotNet.Diagnostics.dotMemory(netcoreapp3.1)`, `BenchmarkDotNet.Diagnostics.dotTrace(net462)`, `BenchmarkDotNet.Diagnostics.dotTrace(netcoreapp3.1)`, `BenchmarkDotNet.Exporters.Plotting`, `BenchmarkDotNet.Exporters.Plotting.Tests(net472)`, `BenchmarkDotNet.IntegrationTests.ConfigPerAssembly(net472)`, `BenchmarkDotNet.IntegrationTests.CustomPaths`, `BenchmarkDotNet.IntegrationTests.DisabledOptimizations(net472)`, `BenchmarkDotNet.IntegrationTests.EnabledOptimizations(net472)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net472)`, `BenchmarkDotNet.IntegrationTests.ManualRunning.MultipleFrameworks(net462)`, `BenchmarkDotNet.IntegrationTests.ManualRunning.MultipleFrameworks(net48)`, `BenchmarkDotNet.IntegrationTests.MonoBenchmarks(net472)`, `BenchmarkDotNet.IntegrationTests.SharedDiagnosers`, `BenchmarkDotNet.IntegrationTests.Static(net472)`, `BenchmarkDotNet.IntegrationTests.VisualBasic(net472)`, `BenchmarkDotNet.IntegrationTests.WasmBenchmarks(net472)`, `BenchmarkDotNet.Samples(net472)`, `BenchmarkDotNet.TestAdapter(net462)`, `BenchmarkDotNet.TestAdapter(netstandard2.0)`, `BenchmarkDotNet.Tests(net472)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/BenchmarkDotNet/Analysers/CompositeAnalyser.cs:6
- `BenchmarkDotNet.Analysers.CompositeAnalyser` (src/BenchmarkDotNet/Analysers/CompositeAnalyser.cs:6) is public, and the library's own code uses it, but no other project in this repository uses it (read: `BenchmarkDotNet.IntegrationTests.ManualRunning.MultipleFrameworks(net8.0)`, `BenchmarkDotNet.IntegrationTests.MonoBenchmarks(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/BenchmarkDotNet/Analysers/CompositeAnalyser.cs:6
- `BenchmarkDotNet.Analysers.CompositeAnalyser` (src/BenchmarkDotNet/Analysers/CompositeAnalyser.cs:6) is public, and the library's own code uses it, but no other project in this repository uses it (read: `BenchmarkDotNet.Analyzers.Tests(net10.0)`, `BenchmarkDotNet.Diagnostics.dotMemory(net10.0)`, `BenchmarkDotNet.Diagnostics.dotTrace(net10.0)`, `BenchmarkDotNet.Exporters.Plotting.Tests(net10.0)`, `BenchmarkDotNet.IntegrationTests`, `BenchmarkDotNet.IntegrationTests.ConfigPerAssembly(net10.0)`, `BenchmarkDotNet.IntegrationTests.DisabledOptimizations(net10.0)`, `BenchmarkDotNet.IntegrationTests.EnabledOptimizations(net10.0)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net10.0)`, `BenchmarkDotNet.IntegrationTests.ManualRunning.MultipleFrameworks(net10.0)`, `BenchmarkDotNet.IntegrationTests.Static(net10.0)`, `BenchmarkDotNet.IntegrationTests.VisualBasic(net10.0)`, `BenchmarkDotNet.IntegrationTests.WasmBenchmarks(net10.0)`, `BenchmarkDotNet.Samples(net10.0)`, `BenchmarkDotNet.Samples.Maui(net10.0-android)`, `BenchmarkDotNet.Samples.Maui(net10.0-ios)`, `BenchmarkDotNet.Samples.Maui(net10.0-maccatalyst)`, `BenchmarkDotNet.Tests(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/BenchmarkDotNet/Analysers/CompositeAnalyser.cs:6
- `BenchmarkDotNet.Analysers.ConclusionHelper` (src/BenchmarkDotNet/Analysers/ConclusionHelper.cs:5) is public, and the library's own code uses it, but no other project in this repository uses it (read: `BenchmarkDotNet.Analyzers.Tests(net472)`, `BenchmarkDotNet.Diagnostics.Windows`, `BenchmarkDotNet.Diagnostics.dotMemory(net462)`, `BenchmarkDotNet.Diagnostics.dotMemory(netcoreapp3.1)`, `BenchmarkDotNet.Diagnostics.dotTrace(net462)`, `BenchmarkDotNet.Diagnostics.dotTrace(netcoreapp3.1)`, `BenchmarkDotNet.Exporters.Plotting`, `BenchmarkDotNet.Exporters.Plotting.Tests(net472)`, `BenchmarkDotNet.IntegrationTests.ConfigPerAssembly(net472)`, `BenchmarkDotNet.IntegrationTests.CustomPaths`, `BenchmarkDotNet.IntegrationTests.DisabledOptimizations(net472)`, `BenchmarkDotNet.IntegrationTests.EnabledOptimizations(net472)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net472)`, `BenchmarkDotNet.IntegrationTests.ManualRunning.MultipleFrameworks(net462)`, `BenchmarkDotNet.IntegrationTests.ManualRunning.MultipleFrameworks(net48)`, `BenchmarkDotNet.IntegrationTests.MonoBenchmarks(net472)`, `BenchmarkDotNet.IntegrationTests.SharedDiagnosers`, `BenchmarkDotNet.IntegrationTests.Static(net472)`, `BenchmarkDotNet.IntegrationTests.VisualBasic(net472)`, `BenchmarkDotNet.IntegrationTests.WasmBenchmarks(net472)`, `BenchmarkDotNet.Samples(net472)`, `BenchmarkDotNet.TestAdapter(net462)`, `BenchmarkDotNet.TestAdapter(netstandard2.0)`, `BenchmarkDotNet.Tests(net472)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/BenchmarkDotNet/Analysers/ConclusionHelper.cs:5
- `BenchmarkDotNet.Analysers.ConclusionHelper` (src/BenchmarkDotNet/Analysers/ConclusionHelper.cs:5) is public, and the library's own code uses it, but no other project in this repository uses it (read: `BenchmarkDotNet.IntegrationTests.ManualRunning.MultipleFrameworks(net8.0)`, `BenchmarkDotNet.IntegrationTests.MonoBenchmarks(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/BenchmarkDotNet/Analysers/ConclusionHelper.cs:5
- `BenchmarkDotNet.Analysers.EnvironmentAnalyser` (src/BenchmarkDotNet/Analysers/EnvironmentAnalyser.cs:11) is public, and the library's own code uses it, but no other project in this repository uses it (read: `BenchmarkDotNet.IntegrationTests.ManualRunning.MultipleFrameworks(net8.0)`, `BenchmarkDotNet.IntegrationTests.MonoBenchmarks(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/BenchmarkDotNet/Analysers/EnvironmentAnalyser.cs:11
- `BenchmarkDotNet.Analysers.HideColumnsAnalyser` (src/BenchmarkDotNet/Analysers/HideColumnsAnalyser.cs:6) is public, and the library's own code uses it, but no other project in this repository uses it (read: `BenchmarkDotNet.Analyzers.Tests(net472)`, `BenchmarkDotNet.Diagnostics.Windows`, `BenchmarkDotNet.Diagnostics.dotMemory(net462)`, `BenchmarkDotNet.Diagnostics.dotMemory(netcoreapp3.1)`, `BenchmarkDotNet.Diagnostics.dotTrace(net462)`, `BenchmarkDotNet.Diagnostics.dotTrace(netcoreapp3.1)`, `BenchmarkDotNet.Exporters.Plotting`, `BenchmarkDotNet.Exporters.Plotting.Tests(net472)`, `BenchmarkDotNet.IntegrationTests.ConfigPerAssembly(net472)`, `BenchmarkDotNet.IntegrationTests.CustomPaths`, `BenchmarkDotNet.IntegrationTests.DisabledOptimizations(net472)`, `BenchmarkDotNet.IntegrationTests.EnabledOptimizations(net472)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net472)`, `BenchmarkDotNet.IntegrationTests.ManualRunning.MultipleFrameworks(net462)`, `BenchmarkDotNet.IntegrationTests.ManualRunning.MultipleFrameworks(net48)`, `BenchmarkDotNet.IntegrationTests.MonoBenchmarks(net472)`, `BenchmarkDotNet.IntegrationTests.SharedDiagnosers`, `BenchmarkDotNet.IntegrationTests.Static(net472)`, `BenchmarkDotNet.IntegrationTests.VisualBasic(net472)`, `BenchmarkDotNet.IntegrationTests.WasmBenchmarks(net472)`, `BenchmarkDotNet.Samples(net472)`, `BenchmarkDotNet.TestAdapter(net462)`, `BenchmarkDotNet.TestAdapter(netstandard2.0)`, `BenchmarkDotNet.Tests(net472)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/BenchmarkDotNet/Analysers/HideColumnsAnalyser.cs:6
- `BenchmarkDotNet.Analysers.HideColumnsAnalyser` (src/BenchmarkDotNet/Analysers/HideColumnsAnalyser.cs:6) is public, and the library's own code uses it, but no other project in this repository uses it (read: `BenchmarkDotNet.IntegrationTests.ManualRunning.MultipleFrameworks(net8.0)`, `BenchmarkDotNet.IntegrationTests.MonoBenchmarks(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/BenchmarkDotNet/Analysers/HideColumnsAnalyser.cs:6
- `BenchmarkDotNet.Analysers.HideColumnsAnalyser` (src/BenchmarkDotNet/Analysers/HideColumnsAnalyser.cs:6) is public, and the library's own code uses it, but no other project in this repository uses it (read: `BenchmarkDotNet.Analyzers.Tests(net10.0)`, `BenchmarkDotNet.Diagnostics.dotMemory(net10.0)`, `BenchmarkDotNet.Diagnostics.dotTrace(net10.0)`, `BenchmarkDotNet.Exporters.Plotting.Tests(net10.0)`, `BenchmarkDotNet.IntegrationTests`, `BenchmarkDotNet.IntegrationTests.ConfigPerAssembly(net10.0)`, `BenchmarkDotNet.IntegrationTests.DisabledOptimizations(net10.0)`, `BenchmarkDotNet.IntegrationTests.EnabledOptimizations(net10.0)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net10.0)`, `BenchmarkDotNet.IntegrationTests.ManualRunning.MultipleFrameworks(net10.0)`, `BenchmarkDotNet.IntegrationTests.Static(net10.0)`, `BenchmarkDotNet.IntegrationTests.VisualBasic(net10.0)`, `BenchmarkDotNet.IntegrationTests.WasmBenchmarks(net10.0)`, `BenchmarkDotNet.Samples(net10.0)`, `BenchmarkDotNet.Samples.Maui(net10.0-android)`, `BenchmarkDotNet.Samples.Maui(net10.0-ios)`, `BenchmarkDotNet.Samples.Maui(net10.0-maccatalyst)`, `BenchmarkDotNet.Tests(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/BenchmarkDotNet/Analysers/HideColumnsAnalyser.cs:6
- `BenchmarkDotNet.Analysers.MinIterationTimeAnalyser` (src/BenchmarkDotNet/Analysers/MinIterationTimeAnalyser.cs:8) is public, and the library's own code uses it, but no other project in this repository uses it (read: `BenchmarkDotNet.Analyzers.Tests(net472)`, `BenchmarkDotNet.Diagnostics.Windows`, `BenchmarkDotNet.Diagnostics.dotMemory(net462)`, `BenchmarkDotNet.Diagnostics.dotMemory(netcoreapp3.1)`, `BenchmarkDotNet.Diagnostics.dotTrace(net462)`, `BenchmarkDotNet.Diagnostics.dotTrace(netcoreapp3.1)`, `BenchmarkDotNet.Exporters.Plotting`, `BenchmarkDotNet.Exporters.Plotting.Tests(net472)`, `BenchmarkDotNet.IntegrationTests.ConfigPerAssembly(net472)`, `BenchmarkDotNet.IntegrationTests.CustomPaths`, `BenchmarkDotNet.IntegrationTests.DisabledOptimizations(net472)`, `BenchmarkDotNet.IntegrationTests.EnabledOptimizations(net472)`, `BenchmarkDotNet.IntegrationTests.ManualRunning(net472)`, `BenchmarkDotNet.IntegrationTests.ManualRunning.MultipleFrameworks(net462)`, `BenchmarkDotNet.IntegrationTests.ManualRunning.MultipleFrameworks(net48)`, `BenchmarkDotNet.IntegrationTests.MonoBenchmarks(net472)`, `BenchmarkDotNet.IntegrationTests.SharedDiagnosers`, `BenchmarkDotNet.IntegrationTests.Static(net472)`, `BenchmarkDotNet.IntegrationTests.VisualBasic(net472)`, `BenchmarkDotNet.IntegrationTests.WasmBenchmarks(net472)`, `BenchmarkDotNet.Samples(net472)`, `BenchmarkDotNet.TestAdapter(net462)`, `BenchmarkDotNet.TestAdapter(netstandard2.0)`, `BenchmarkDotNet.Tests(net472)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/BenchmarkDotNet/Analysers/MinIterationTimeAnalyser.cs:8
What to do
- Make `BenchmarkDotNet.Diagnostics.Windows.ConcurrencyVisualizerProfiler` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `BenchmarkDotNet.Diagnostics.Windows.EtwProfiler` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `BenchmarkDotNet.Diagnostics.Windows.HardwareCounters` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `BenchmarkDotNet.Diagnostics.Windows.InliningDiagnoser` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `BenchmarkDotNet.Diagnostics.Windows.JitStatsDiagnoser` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `BenchmarkDotNet.Diagnostics.Windows.NativeMemoryProfiler` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `BenchmarkDotNet.Diagnostics.Windows.TailCallDiagnoser` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `BenchmarkDotNet.Diagnostics.Windows.Tracing.EngineEventLogParser` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `BenchmarkDotNet.Diagnostics.Windows.Tracing.NativeMemoryLogParser` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `BenchmarkDotNet.Diagnostics.Windows.Tracing.TraceLogParser` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `BenchmarkDotNet.Diagnostics.Windows.Tracing.ProcessMetrics` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `BenchmarkDotNet.Diagnostics.Windows.Tracing.IterationData` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `BenchmarkDotNet.Analysers.BaselineCustomAnalyzer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `BenchmarkDotNet.Analysers.BaselineCustomAnalyzer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `BenchmarkDotNet.Analysers.BaselineCustomAnalyzer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `BenchmarkDotNet.Analysers.CompositeAnalyser` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `BenchmarkDotNet.Analysers.CompositeAnalyser` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `BenchmarkDotNet.Analysers.CompositeAnalyser` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `BenchmarkDotNet.Analysers.ConclusionHelper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `BenchmarkDotNet.Analysers.ConclusionHelper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `BenchmarkDotNet.Analysers.EnvironmentAnalyser` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `BenchmarkDotNet.Analysers.HideColumnsAnalyser` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `BenchmarkDotNet.Analysers.HideColumnsAnalyser` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `BenchmarkDotNet.Analysers.HideColumnsAnalyser` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `BenchmarkDotNet.Analysers.MinIterationTimeAnalyser` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
P3 · Security & performance tooling
- `build/BenchmarkDotNet.Build/BenchmarkDotNet.Build.csproj` 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`. — build/BenchmarkDotNet.Build/BenchmarkDotNet.Build.csproj:10
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
P7 · Outbound HTTP resilience
- `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. This codebase ships libraries/tools rather than a service it operates, so the failure lands as a hung caller — a build step, a CLI run, a UI thread — with no way out. — build/BenchmarkDotNet.Build/Meta/Repo.cs:24
What to do
- Give every outbound call a bound the caller can rely on: set an explicit `HttpClient.Timeout` (or pass a `CancellationToken` from a `CancellationTokenSource` with a deadline) and flow the caller's own `CancellationToken` through, so a slow endpoint fails fast instead of hanging.
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
- 16 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
- `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×10) — src/BenchmarkDotNet.Diagnostics.dotMemory/DotMemoryDiagnoser.cs:16, src/BenchmarkDotNet.Diagnostics.dotTrace/DotTraceDiagnoser.cs:16, src/BenchmarkDotNet/Engines/TcpHost.cs:61, …
- `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×6) — build/BenchmarkDotNet.Build/Runners/DocumentationRunner.cs:111, build/BenchmarkDotNet.Build/Runners/DocumentationRunner.cs:112, build/BenchmarkDotNet.Build/Runners/ReleaseRunner.cs:84, …
What to do
- Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
S1 · Cryptographic Hygiene
- MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses. (×2) — samples/BenchmarkDotNet.Samples/IntroFluentConfigBuilder.cs:16, samples/BenchmarkDotNet.Samples/IntroStatisticsColumns.cs:12
What to do
- Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (`System.IO.Hashing.XxHash64`/`Crc32`) where it only derives an identifier such as a cache key or a mutex name. This repository constructs a collision-broken hash (MD5/SHA1) at 2 sites, not one: `samples/BenchmarkDotNet.Samples/IntroFluentConfigBuilder.cs:16` (MD5), `samples/BenchmarkDotNet.Samples/IntroStatisticsColumns.cs:12` (MD5). Each is a separate decision — fixing only the line this row cites leaves the others in place.
X1 · Async correctness
- Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×8) — src/BenchmarkDotNet.Diagnostics.dotMemory/DotMemoryDiagnoser.cs:16, src/BenchmarkDotNet.Diagnostics.dotTrace/DotTraceDiagnoser.cs:16, src/BenchmarkDotNet/Helpers/AwaitHelper.cs:53, …
- `Engine.SleepIfPositive` is a synchronous helper that blocks (`Thread.Sleep`): called from an `async` method it parks the thread exactly as the inline call would. Make the helper `async` and `await` it (`await Task.Delay`, `SemaphoreSlim.WaitAsync`, a `TaskCompletionSource` instead of the poll). — src/BenchmarkDotNet/Engines/Engine.cs:213
- Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` wastes a thread and, if the task needs a context this one is holding, deadlocks. `Dispose()` returns void by contract, so it cannot simply `await`: signal the work to stop first (cancel its token, set its stop flag) so the wait is short, give the wait a TIMEOUT so a hung task cannot hang shutdown, and — where callers can use it — add an awaitable teardown (`DisposeAsync`/`StopAsync`) beside the synchronous one and let `Dispose()` remain the bounded fallback. (×2) — src/BenchmarkDotNet/Engines/TcpHost.cs:61, src/BenchmarkDotNet/Helpers/ProcessCleanupHelper.cs:44
- `Thread.Sleep` parks the thread for the whole delay: no other work runs on it, and under load the pool must grow to make up for it. `await Task.Delay(…)` suspends only this method. — src/BenchmarkDotNet/Engines/TcpHost.cs:83
- `.Wait(…)` blocks this thread until the task completes or the bound expires — sync-over-async: it can deadlock under a synchronization context and it parks a thread while it waits. `await` the task (with `.WaitAsync(timeout, token)` where the bound matters). — src/BenchmarkDotNet/Helpers/ProcessHelper.cs:56
- `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. (×7) — src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/BenchmarkActionImpl.cs:287, src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/BenchmarkActionImpl.cs:361, src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/BenchmarkActionImpl.cs:437, …
What to do
- Sync-over-async (deadlock risk)
X12 · Unreachable branch
X13 · Undrained process stream
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
- `md5` (line 16) holds a `MD5` that `Algo_Md5VsSha256` acquires itself — every assignment to it is a call that opens or creates a new instance for the caller to own — and nothing in `Algo_Md5VsSha256` ever releases it: the type is not `IDisposable`, declares no `Dispose`, and every other mention of `md5` only reads through it, so it is never disposed, closed, returned or handed on. Whatever it opened (a connection, a channel, a file) stays open until finalization if the type has a finalizer and until the process ends if it does not, once per instance of `Algo_Md5VsSha256`. Implement `IDisposable` and release `md5` there, or take the instance from the caller so its owner ends it. — samples/BenchmarkDotNet.Samples/IntroFluentConfigBuilder.cs:16
- `sha256` (line 17) holds a `SHA256` that `Algo_Md5VsSha256` acquires itself — every assignment to it is a call that opens or creates a new instance for the caller to own — and nothing in `Algo_Md5VsSha256` ever releases it: the type is not `IDisposable`, declares no `Dispose`, and every other mention of `sha256` only reads through it, so it is never disposed, closed, returned or handed on. Whatever it opened (a connection, a channel, a file) stays open until finalization if the type has a finalizer and until the process ends if it does not, once per instance of `Algo_Md5VsSha256`. Implement `IDisposable` and release `sha256` there, or take the instance from the caller so its owner ends it. — samples/BenchmarkDotNet.Samples/IntroFluentConfigBuilder.cs:17
- `md5` (line 12) holds a `MD5` that `IntroStatisticsColumns` acquires itself — every assignment to it is a call that opens or creates a new instance for the caller to own — and nothing in `IntroStatisticsColumns` ever releases it: the type is not `IDisposable`, declares no `Dispose`, and every other mention of `md5` only reads through it, so it is never disposed, closed, returned or handed on. Whatever it opened (a connection, a channel, a file) stays open until finalization if the type has a finalizer and until the process ends if it does not, once per instance of `IntroStatisticsColumns`. Implement `IDisposable` and release `md5` there, or take the instance from the caller so its owner ends it. — samples/BenchmarkDotNet.Samples/IntroStatisticsColumns.cs:12
- `sha256` (line 13) holds a `SHA256` that `IntroStatisticsColumns` acquires itself — every assignment to it is a call that opens or creates a new instance for the caller to own — and nothing in `IntroStatisticsColumns` ever releases it: the type is not `IDisposable`, declares no `Dispose`, and every other mention of `sha256` only reads through it, so it is never disposed, closed, returned or handed on. Whatever it opened (a connection, a channel, a file) stays open until finalization if the type has a finalizer and until the process ends if it does not, once per instance of `IntroStatisticsColumns`. Implement `IDisposable` and release `sha256` there, or take the instance from the caller so its owner ends it. — samples/BenchmarkDotNet.Samples/IntroStatisticsColumns.cs:13
- `plt` is a `Plot`, which implements `IDisposable`, and it is created here (line 181). Every use of it in `CreateBarPlot` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var plt = …;`), which releases it at the end of the scope on every path including a throw. — src/BenchmarkDotNet.Exporters.Plotting/ScottPlotExporter.cs:181
- `plt` is a `Plot`, which implements `IDisposable`, and it is created here (line 257). Every use of it in `CreateBoxPlot` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var plt = …;`), which releases it at the end of the scope on every path including a throw. — src/BenchmarkDotNet.Exporters.Plotting/ScottPlotExporter.cs:257
- `writer` is never created by `TextLogger` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 20). Its declared type `TextWriter` is an abstract class, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — src/BenchmarkDotNet/Loggers/TextLogger.cs:20
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X2 · Cancellation propagation
- Only 154/172 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
- No CancellationToken parameter — the body observes an ambient token instead (a field or a context object), so the work does stop on cancellation, but a caller cannot cancel this call independently of the owner that created that token. (×10) — samples/BenchmarkDotNet.Samples/IntroCancellationToken.cs:17, src/BenchmarkDotNet/Engines/Engine.cs:63, src/BenchmarkDotNet/Engines/Engine.cs:93, …
- No CancellationToken parameter — this work can't be stopped early once started. (×7) — src/BenchmarkDotNet/Engines/Engine.cs:284, src/BenchmarkDotNet/Engines/FileStdOutConnection.cs:21, src/BenchmarkDotNet/Engines/WebSocketConnection.cs:13, …
- Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one. — src/BenchmarkDotNet/Loggers/Broker.cs:92
- 1 async method(s) await work their caller's cancellation cannot reach: a CancellationToken they hold (a parameter, or the one a framework-fixed signature carries) is never passed on, or the call is handed CancellationToken.None, default or an already-cancelled token. Forward the caller's token to that call.
- Holds a CancellationToken but hands `CancellationToken.None` to the awaited call on this line, so the caller's cancellation never reaches that work. Pass the token on (or, where the work must outlive the caller, start it without awaiting it so the choice is visible). — src/BenchmarkDotNet/Loggers/Broker.cs:94
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×15) — samples/BenchmarkDotNet.Samples/IntroExceptionDiagnoser.cs:18, src/BenchmarkDotNet/Detectors/OsDetector.cs:51, src/BenchmarkDotNet/Engines/FileStdOutListener.cs:33, …
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else). (×3) — src/BenchmarkDotNet/Engines/TcpHost.cs:62, src/BenchmarkDotNet/Helpers/ProcessCleanupHelper.cs:47, src/BenchmarkDotNet/Helpers/ProcessCleanupHelper.cs:78
- `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. (×2) — src/BenchmarkDotNet/Extensions/PathFeatures.cs:89, src/BenchmarkDotNet/Toolchains/CsProj/CsProjBuilder.cs:620
- `catch (NotSupportedException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/BenchmarkDotNet/Validators/JitOptimizationsValidator.cs:25
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X4 · Structured logging
X5 · Nullable reference types
- This method contradicts itself about `targetMethod`: line 120 writes `targetMethod?.HasAttribute`, which says `targetMethod` can be null, but line 113 then dereferences it directly as `targetMethod.IsStatic` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `targetMethod` truly cannot be null here, the `?.` is misleading. Settle it one way — test `targetMethod` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/BenchmarkActionFactory.cs:113
- ~1.6 `!` suppressions per 1k syntax nodes — 464 suppression(s) across the 295087 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
- Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 64% | Adequate | Acceptable, with room to improve. |
| Architecture | 73% | Adequate — gated by AX2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 64% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 65% | Adequate — gated by P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 33% | Weak — gated by D28, D29, D36, C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 77% | Strong | Strongest area. |
Unscored — 4 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 2 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- 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 — 17 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 27 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 45 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — no DI registrations detected
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — 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.
- 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.
- D11 Test Reliability — Test runner surfaced no tests
- D12 Dependency Hygiene — Dependency hygiene not measured — pkgs.dev.azure.com could not be reached
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; F#, JavaScript, Visual Basic 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.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 79 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — no coverage collector is wired up
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 5 strongly-typed id(s); 36 value object(s)
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (5 event handler(s))
- ED5 Idempotency — 5 mutating command handler(s)/consumer(s) detected and 100 handler method(s) walked, but no persistent write was recognised in any of them — idempotency not assessed
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- 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.
- 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
- 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
- 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
- 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 — 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
- 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
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 159 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- NoWarnInCsproj — 9 warning codes suppressed in one element src/BenchmarkDotNet/BenchmarkDotNet.csproj:8
- NoWarnInCsproj — 8 warning codes suppressed in one element src/BenchmarkDotNet.Annotations/BenchmarkDotNet.Annotations.csproj:6
- NoWarnInCsproj — 8 warning codes suppressed in one element src/BenchmarkDotNet.Diagnostics.Windows/BenchmarkDotNet.Diagnostics.Windows.csproj:7
- NoWarnInCsproj build/BenchmarkDotNet.Build/BenchmarkDotNet.Build.csproj:7
- NoWarnInCsproj tests/BenchmarkDotNet.IntegrationTests/BenchmarkDotNet.IntegrationTests.csproj:14
- NoWarnInCsproj tests/BenchmarkDotNet.IntegrationTests.RuntimeAsync/BenchmarkDotNet.IntegrationTests.RuntimeAsync.csproj:15
- NoWarnInCsproj tests/BenchmarkDotNet.Tests/BenchmarkDotNet.Tests.csproj:10
- NoWarnInCsproj samples/Directory.Build.props:5
- NoWarnInCsproj tests/Directory.Build.props:5
- NoWarnInCsproj src/BenchmarkDotNet.Analyzers/BenchmarkDotNet.Analyzers.csproj:11
- NoWarnInCsproj src/BenchmarkDotNet.Diagnostics.dotMemory/BenchmarkDotNet.Diagnostics.dotMemory.csproj:5
- NoWarnInCsproj src/BenchmarkDotNet.Diagnostics.dotTrace/BenchmarkDotNet.Diagnostics.dotTrace.csproj:5
- NoWarnInCsproj src/BenchmarkDotNet.Weaver/BenchmarkDotNet.Weaver.csproj:14
- NoWarnInCsproj src/BenchmarkDotNet.Weaver/BenchmarkDotNet.Weaver.csproj:14
- NoWarnInCsproj src/BenchmarkDotNet.Weaver/BenchmarkDotNet.Weaver.csproj:14
- NoWarnInCsproj tests/BenchmarkDotNet.Analyzers.Tests/BenchmarkDotNet.Analyzers.Tests.csproj:11
- NoWarnInCsproj build/roslynBands.props:7
- NoWarnInCsproj tests/BenchmarkDotNet.IntegrationTests/BenchmarkDotNet.IntegrationTests.csproj:14
- NoWarnInCsproj tests/BenchmarkDotNet.Tests/BenchmarkDotNet.Tests.csproj:10
- NoWarnInCsproj tests/BenchmarkDotNet.Tests/BenchmarkDotNet.Tests.csproj:10
- NoWarnInCsproj tests/BenchmarkDotNet.Tests/BenchmarkDotNet.Tests.csproj:10
- NoWarnInCsproj tests/BenchmarkDotNet.Tests/BenchmarkDotNet.Tests.csproj:10
- EmptyCatchBlock samples/BenchmarkDotNet.Samples/IntroExceptionDiagnoser.cs:18
- EmptyCatchBlock src/BenchmarkDotNet/Detectors/OsDetector.cs:51
- EmptyCatchBlock src/BenchmarkDotNet/Engines/FileStdOutListener.cs:33
- EmptyCatchBlock src/BenchmarkDotNet/Engines/TcpHost.cs:62
- EmptyCatchBlock src/BenchmarkDotNet/Environments/PhysicalMemoryInfo.cs:87
- EmptyCatchBlock src/BenchmarkDotNet/Environments/PhysicalMemoryInfo.cs:184
- EmptyCatchBlock src/BenchmarkDotNet/Environments/PhysicalMemoryInfo.cs:210
- EmptyCatchBlock src/BenchmarkDotNet/Environments/PhysicalMemoryInfo.cs:381
- EmptyCatchBlock REDACTED:158
- EmptyCatchBlock src/BenchmarkDotNet/Helpers/FileCleanupHelper.cs:52
- EmptyCatchBlock src/BenchmarkDotNet/Helpers/PowerShellLocator.cs:43
- EmptyCatchBlock src/BenchmarkDotNet/Helpers/ProcessCleanupHelper.cs:47
- EmptyCatchBlock src/BenchmarkDotNet/Helpers/ProcessCleanupHelper.cs:78
- EmptyCatchBlock src/BenchmarkDotNet/Helpers/ProcessCleanupHelper.cs:94
- EmptyCatchBlock src/BenchmarkDotNet/Helpers/ProcessHelper.cs:167
- EmptyCatchBlock src/BenchmarkDotNet/Loggers/LinqPadLogger.cs:28
- EmptyCatchBlock src/BenchmarkDotNet/Running/ConsoleTitler.cs:53
- EmptyCatchBlock src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Runnable/RunnableReflectionHelpers.cs:26
- WriteOnlyPrivateField src/BenchmarkDotNet/Engines/Consumer.cs:10
- WriteOnlyPrivateField src/BenchmarkDotNet/Engines/Consumer.cs:11
- WriteOnlyPrivateField src/BenchmarkDotNet/Engines/Consumer.cs:12
- WriteOnlyPrivateField src/BenchmarkDotNet/Engines/Consumer.cs:13
- WriteOnlyPrivateField src/BenchmarkDotNet/Engines/Consumer.cs:14
- WriteOnlyPrivateField src/BenchmarkDotNet/Engines/Consumer.cs:15
- WriteOnlyPrivateField src/BenchmarkDotNet/Engines/Consumer.cs:16
- WriteOnlyPrivateField src/BenchmarkDotNet/Engines/Consumer.cs:17
- WriteOnlyPrivateField src/BenchmarkDotNet/Engines/Consumer.cs:18
- WriteOnlyPrivateField src/BenchmarkDotNet/Engines/Consumer.cs:22
- WriteOnlyPrivateField src/BenchmarkDotNet/Engines/Consumer.cs:23
- WriteOnlyPrivateField src/BenchmarkDotNet/Engines/Consumer.cs:24
- WriteOnlyPrivateField tests/BenchmarkDotNet.Tests/ParamsSourceTests.cs:106
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FileScopedPragmaDisable tests/BenchmarkDotNet.Tests/CodeGeneratorTests.cs:68
- FileScopedPragmaDisable tests/BenchmarkDotNet.Tests/Validators/ParamsValidatorTests.cs:5
- FileScopedPragmaDisable tests/BenchmarkDotNet.Tests/Validators/SourceReturnTypeValidatorTests.cs:5
- FileScopedPragmaDisable tests/BenchmarkDotNet.Tests/Validators/SourceReturnTypeValidatorTests.cs:6
- FileScopedPragmaDisable tests/BenchmarkDotNet.Tests/Validators/SourceReturnTypeValidatorTests.cs:7
- FileScopedPragmaDisable tests/BenchmarkDotNet.Tests/Validators/SourceReturnTypeValidatorTests.cs:8
- FileScopedPragmaDisable tests/BenchmarkDotNet.Tests/Validators/SourceReturnTypeValidatorTests.cs:9
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Boundary-crossing change coupling: RuntimeMoniker.cs ↔ ConfigParser.cs src/BenchmarkDotNet.Annotations/Jobs/RuntimeMoniker.cs:1
- Boundary-crossing change coupling: RuntimeMoniker.cs ↔ DotTraceDiagnoser.cs src/BenchmarkDotNet.Annotations/Jobs/RuntimeMoniker.cs:1
- Boundary-crossing change coupling: RuntimeMoniker.cs ↔ DotMemoryDiagnoser.cs src/BenchmarkDotNet.Annotations/Jobs/RuntimeMoniker.cs:1
- Namespace dependency cycle src/BenchmarkDotNet/Analysers/ConclusionHelper.cs:1
- Namespace dependency cycle build/BenchmarkDotNet.Build/BuildContext.cs:7
- REDACTED
- REDACTED
- DemotedWarningsAsErrors tests/BenchmarkDotNet.IntegrationTests.ManualRunning.MultipleFrameworks/BenchmarkDotNet.IntegrationTests.ManualRunning.MultipleFrameworks.csproj:8
- REDACTED
- REDACTED
Serious — 485 finding(s)
- BarePragmaDisable samples/BenchmarkDotNet.Samples/IntroNativeMemory.cs:14
- BarePragmaDisable src/BenchmarkDotNet/Diagnosers/CompositeDiagnoser.cs:67
- BarePragmaDisable src/BenchmarkDotNet/Running/BenchmarkRunnerClean.cs:407
- BarePragmaDisable src/BenchmarkDotNet/Running/BenchmarkRunnerClean.cs:724
- BarePragmaDisable src/BenchmarkDotNet/Validators/CompositeValidator.cs:34
- BarePragmaDisable src/BenchmarkDotNet/Validators/DiagnosersValidator.cs:25
- BarePragmaDisable tests/BenchmarkDotNet.Tests/Validators/SynchronizationContextCaptureTests.cs:81
- BarePragmaDisable tests/BenchmarkDotNet.Exporters.Plotting.Tests/ScottPlotExporterTests.cs:263
- BarePragmaDisable tests/BenchmarkDotNet.IntegrationTests/BaselineRatioColumnTest.cs:106
- BarePragmaDisable tests/BenchmarkDotNet.Tests/Exporters/MarkdownExporterVerifyTests.cs:232
- BarePragmaDisable tests/BenchmarkDotNet.IntegrationTests/DeclarationErrorTests.cs:31
- BarePragmaDisable tests/BenchmarkDotNet.Tests/Running/BenchmarkConverterTests.cs:294
- BarePragmaDisable tests/BenchmarkDotNet.IntegrationTests/DeclarationErrorTests.cs:51
- BarePragmaDisable tests/BenchmarkDotNet.IntegrationTests/DeclarationErrorTests.cs:71
- BarePragmaDisable tests/BenchmarkDotNet.IntegrationTests/DeclarationErrorTests.cs:87
- BarePragmaDisable tests/BenchmarkDotNet.Tests/ParamsSourceTests.cs:856
- BarePragmaDisable tests/BenchmarkDotNet.IntegrationTests/RunningEmptyBenchmarkTests.cs:38
- BarePragmaDisable tests/BenchmarkDotNet.IntegrationTests/RunningEmptyBenchmarkTests.cs:82
- BarePragmaDisable tests/BenchmarkDotNet.Tests/Attributes/ParamsAllValuesVerifyTests.cs:109
- BarePragmaDisable tests/BenchmarkDotNet.Tests/Attributes/ParamsAllValuesVerifyTests.cs:120
- BarePragmaDisable tests/BenchmarkDotNet.Tests/Attributes/ParamsAllValuesVerifyTests.cs:131
- BarePragmaDisable tests/BenchmarkDotNet.Tests/GenericBuilderTests.cs:77
- BarePragmaDisable tests/BenchmarkDotNet.Tests/ParamsSourceTests.cs:718
- BarePragmaDisable tests/BenchmarkDotNet.Tests/RefStructSourceTests.cs:30
- BarePragmaDisable tests/BenchmarkDotNet.Tests/RefStructSourceTests.cs:51
- TodoComment src/BenchmarkDotNet.Analyzers/BenchmarkRunner/RunAnalyzer.cs:141
- TodoComment src/BenchmarkDotNet.Exporters.Plotting/ScottPlotExporter.cs:129
- TodoComment src/BenchmarkDotNet.TestAdapter/VSTestEventProcessor.cs:97
- TodoComment src/BenchmarkDotNet/Analysers/Conclusion.cs:5
- TodoComment src/BenchmarkDotNet/Analysers/OutliersAnalyser.cs:24
- TodoComment src/BenchmarkDotNet/Engines/RunResults.cs:77
- TodoComment src/BenchmarkDotNet/Attributes/Exporters/MarkdownExporterAttribute.cs:6
- TodoComment src/BenchmarkDotNet/Characteristics/Characteristic.cs:71
- TodoComment src/BenchmarkDotNet/Characteristics/CharacteristicObject.cs:8
- TodoComment src/BenchmarkDotNet/Characteristics/CharacteristicPresenter.cs:82
- TodoComment src/BenchmarkDotNet/Columns/DefaultColumnProvider.cs:82
- TodoComment src/BenchmarkDotNet/Columns/UnitType.cs:3
- TodoComment src/BenchmarkDotNet/ConsoleArguments/ListBenchmarks/BenchmarkCaseJsonConverter.cs:23
- TodoComment src/BenchmarkDotNet/Detectors/OsDetector.cs:93
- TodoComment src/BenchmarkDotNet/Diagnosers/SpeedScopeExporter.cs:23
- TodoComment src/BenchmarkDotNet/Disassemblers/Arm64Disassembler.cs:154
- TodoComment src/BenchmarkDotNet/Disassemblers/MonoDisassembler.cs:45
- TodoComment src/BenchmarkDotNet/Disassemblers/MonoDisassembler.cs:46
- TodoComment src/BenchmarkDotNet/Engines/EnginePilotStage.cs:9
- TodoComment src/BenchmarkDotNet/Engines/EngineStage.cs:80
- TodoComment src/BenchmarkDotNet/Environments/EnvironmentResolver.cs:23
- TodoComment src/BenchmarkDotNet/Environments/EnvironmentResolver.cs:28
- TodoComment src/BenchmarkDotNet/Exporters/Csv/CsvHelper.cs:3
- TodoComment src/BenchmarkDotNet/Exporters/Json/JsonExporterBase.cs:82
- TodoComment src/BenchmarkDotNet/Exporters/MarkdownExporter.cs:117
- Swallowed exception (empty catch) samples/BenchmarkDotNet.Samples/IntroExceptionDiagnoser.cs:18
- Swallowed exception (empty catch) src/BenchmarkDotNet/Detectors/OsDetector.cs:51
- Swallowed exception (empty catch) src/BenchmarkDotNet/Engines/FileStdOutListener.cs:33
- Swallowed exception (empty catch) src/BenchmarkDotNet/Engines/TcpHost.cs:62
- Swallowed exception (empty catch) src/BenchmarkDotNet/Environments/PhysicalMemoryInfo.cs:87
- Swallowed exception (empty catch) src/BenchmarkDotNet/Environments/PhysicalMemoryInfo.cs:184
- Swallowed exception (empty catch) src/BenchmarkDotNet/Environments/PhysicalMemoryInfo.cs:210
- Swallowed exception (empty catch) src/BenchmarkDotNet/Environments/PhysicalMemoryInfo.cs:381
- Swallowed exception (empty catch) REDACTED:158
- Swallowed exception (empty catch) src/BenchmarkDotNet/Helpers/FileCleanupHelper.cs:52
- Swallowed exception (empty catch) src/BenchmarkDotNet/Helpers/PowerShellLocator.cs:43
- Swallowed exception (empty catch) src/BenchmarkDotNet/Helpers/ProcessCleanupHelper.cs:47
- Swallowed exception (empty catch) src/BenchmarkDotNet/Helpers/ProcessCleanupHelper.cs:78
- Swallowed exception (empty catch) src/BenchmarkDotNet/Helpers/ProcessCleanupHelper.cs:94
- Swallowed exception (empty catch) src/BenchmarkDotNet/Helpers/ProcessHelper.cs:167
- Swallowed exception (empty catch) src/BenchmarkDotNet/Loggers/LinqPadLogger.cs:28
- Swallowed exception (empty catch) src/BenchmarkDotNet/Running/ConsoleTitler.cs:53
- Swallowed exception (empty catch) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Runnable/RunnableReflectionHelpers.cs:26
- Sync-over-async blocking
- Sync-over-async blocking src/BenchmarkDotNet.Diagnostics.dotMemory/DotMemoryDiagnoser.cs:16
- Sync-over-async blocking src/BenchmarkDotNet.Diagnostics.dotTrace/DotTraceDiagnoser.cs:16
- Sync-over-async blocking src/BenchmarkDotNet/Engines/TcpHost.cs:61
- Sync-over-async blocking src/BenchmarkDotNet/Helpers/AwaitHelper.cs:53
- Sync-over-async blocking src/BenchmarkDotNet/Helpers/AwaitHelper.cs:55
- Sync-over-async blocking src/BenchmarkDotNet/Helpers/AwaitHelper.cs:175
- Sync-over-async blocking src/BenchmarkDotNet/Helpers/AwaitHelper.cs:206
- Sync-over-async blocking src/BenchmarkDotNet/Helpers/AwaitHelper.cs:238
- Sync-over-async blocking src/BenchmarkDotNet/Helpers/AwaitHelper.cs:270
- Sync-over-async blocking src/BenchmarkDotNet/Helpers/ProcessCleanupHelper.cs:44
- Sync-over-async blocking build/BenchmarkDotNet.Build/Runners/DocumentationRunner.cs:111
- Sync-over-async blocking build/BenchmarkDotNet.Build/Runners/DocumentationRunner.cs:112
- Sync-over-async blocking build/BenchmarkDotNet.Build/Runners/ReleaseRunner.cs:84
- Sync-over-async blocking build/BenchmarkDotNet.Build/Runners/ReleaseRunner.cs:138
- Sync-over-async blocking build/BenchmarkDotNet.Build/Runners/ReleaseRunner.cs:144
- Sync-over-async blocking build/BenchmarkDotNet.Build/Runners/ReleaseRunner.cs:192
- Sync-over-async (deadlock risk) src/BenchmarkDotNet.Diagnostics.dotMemory/DotMemoryDiagnoser.cs:16
- Sync-over-async (deadlock risk) src/BenchmarkDotNet.Diagnostics.dotTrace/DotTraceDiagnoser.cs:16
- Sync-over-async (deadlock risk) src/BenchmarkDotNet/Engines/TcpHost.cs:61
- Sync-over-async (deadlock risk) src/BenchmarkDotNet/Helpers/AwaitHelper.cs:53
- Sync-over-async (deadlock risk) src/BenchmarkDotNet/Helpers/AwaitHelper.cs:55
- Sync-over-async (deadlock risk) src/BenchmarkDotNet/Helpers/AwaitHelper.cs:175
- Sync-over-async (deadlock risk) src/BenchmarkDotNet/Helpers/AwaitHelper.cs:206
- Sync-over-async (deadlock risk) src/BenchmarkDotNet/Helpers/AwaitHelper.cs:238
- Sync-over-async (deadlock risk) src/BenchmarkDotNet/Helpers/AwaitHelper.cs:270
- Sync-over-async (deadlock risk) src/BenchmarkDotNet/Helpers/ProcessCleanupHelper.cs:44
- CommentedOutCode src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:378
- CommentedOutCode src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncStateMachineEmitter.cs:372
- CommentedOutCode src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/RuntimeAsyncEmitter.cs:75
- CommentedOutCode tests/BenchmarkDotNet.IntegrationTests/JitRuntimeValidationTest.cs:36
- CommentedOutCode tests/BenchmarkDotNet.Tests/Analysers/ZeroMeasurementHelperTests.cs:46
- CommentedOutCode tests/BenchmarkDotNet.Tests/Analysers/ZeroMeasurementHelperTests.cs:102
- CommentedOutCode src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/RunnableEmitter.cs:300
- CommentedOutCode tests/BenchmarkDotNet.Tests/Analysers/ZeroMeasurementHelperTests.cs:16
- CommentedOutCode tests/BenchmarkDotNet.Tests/Analysers/ZeroMeasurementHelperTests.cs:144
- Hotspot: src/BenchmarkDotNet/ConsoleArguments/ConfigParser.cs src/BenchmarkDotNet/ConsoleArguments/ConfigParser.cs:279
- Hotspot: src/BenchmarkDotNet.Analyzers/Attributes/ArgumentsAttributeAnalyzer.cs src/BenchmarkDotNet.Analyzers/Attributes/ArgumentsAttributeAnalyzer.cs:138
- Hotspot: src/BenchmarkDotNet/Running/BenchmarkRunnerClean.cs src/BenchmarkDotNet/Running/BenchmarkRunnerClean.cs:208
- Hotspot: src/BenchmarkDotNet/Disassemblers/ClrMdDisassembler.cs src/BenchmarkDotNet/Disassemblers/ClrMdDisassembler.cs:269
- Hotspot: src/BenchmarkDotNet.Analyzers/Attributes/GeneralParameterAttributesAnalyzer.cs src/BenchmarkDotNet.Analyzers/Attributes/GeneralParameterAttributesAnalyzer.cs:348
- Hotspot: src/BenchmarkDotNet/Environments/Runtimes/CoreRuntime.cs src/BenchmarkDotNet/Environments/Runtimes/CoreRuntime.cs:108
- Hotspot: src/BenchmarkDotNet.Analyzers/Attributes/ParamsAttributeAnalyzer.cs src/BenchmarkDotNet.Analyzers/Attributes/ParamsAttributeAnalyzer.cs:61
- async void method: StartWorkload src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/BenchmarkActionImpl.cs:287
- async void method: StartWorkload src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/BenchmarkActionImpl.cs:361
- async void method: StartWorkload src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/BenchmarkActionImpl.cs:437
- async void method: StartWorkload src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/BenchmarkActionImpl.cs:511
- async void method: StartWorkload src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/BenchmarkActionImpl.cs:589
- async void method: StartWorkload src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/BenchmarkActionImpl.cs:668
- async void method: Button_Clicked samples/BenchmarkDotNet.Samples.Maui/MainPage.xaml.cs:16
- Async method without CancellationToken: RandomizeManagedHeapMemory src/BenchmarkDotNet/Engines/Engine.cs:284
- Async method without CancellationToken: WriteLineAsync src/BenchmarkDotNet/Engines/FileStdOutConnection.cs:21
- Async method without CancellationToken: WriteLineAsync src/BenchmarkDotNet/Engines/WebSocketConnection.cs:13
- Async method without CancellationToken: DisposeAllAsync src/BenchmarkDotNet/Helpers/DisposeHelper.cs:7
- Async method without CancellationToken: StopReadAsync src/BenchmarkDotNet/Loggers/AsyncProcessOutputReader.cs:86
- Async method without CancellationToken: GetSupportedBenchmarks src/BenchmarkDotNet/Running/BenchmarkRunnerClean.cs:694
- Async method without CancellationToken: Button_Clicked samples/BenchmarkDotNet.Samples.Maui/MainPage.xaml.cs:16
- Process-global static state: DefaultConfig src/BenchmarkDotNet/Configs/DefaultConfig.cs:19
- Process-global static state: HostEnvironmentInfo src/BenchmarkDotNet/Environments/HostEnvironmentInfo.cs:22
- Process-global static state: PathFeatures src/BenchmarkDotNet/Extensions/PathFeatures.cs:12
- Process-global static state: UserInteraction src/BenchmarkDotNet/Running/UserInteraction.cs:10
- Process-global static state: JsHost src/BenchmarkDotNet/Engines/JsHost.cs:13
- Process-global static state: MarkdownBuilder build/BenchmarkDotNet.Build/Runners/Changelog/ChangelogDetailsBuilder.cs:31
- Stateful shared instance: EventPipeProfiler src/BenchmarkDotNet/Diagnosers/EventPipeProfiler.cs:17
- Stateful shared instance: ExceptionDiagnoser src/BenchmarkDotNet/Diagnosers/ExceptionDiagnoser.cs:18
- Stateful shared instance: PerfCollectProfiler REDACTED:24
- Stateful shared instance: ThreadingDiagnoser src/BenchmarkDotNet/Diagnosers/ThreadingDiagnoser.cs:17
- Stateful shared instance: ConsoleLogger src/BenchmarkDotNet/Loggers/ConsoleLogger.cs:9
- MethodTooLong: AsyncEnumerableCoreEmitter.EmitWorkloadCore src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncEnumerableCoreEmitter.cs:49
- MethodTooLong: AsyncCoreEmitter.EmitWorkloadCore src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:25
- MethodTooLong: BenchmarkClassAnalyzer.AnalyzeClassDeclaration src/BenchmarkDotNet.Analyzers/General/BenchmarkClassAnalyzer.cs:112
- MethodTooLong: ArgumentsAttributeAnalyzer.AnalyzeMethodSymbol src/BenchmarkDotNet.Analyzers/Attributes/ArgumentsAttributeAnalyzer.cs:138
- MethodTooLong: NativeMemoryLogParser.Parse src/BenchmarkDotNet.Diagnostics.Windows/Tracing/NativeMemoryLogParser.cs:65
- Change coupling: InProcessEmitExecutor.cs ↔ InProcessNoEmitExecutor.cs src/BenchmarkDotNet/Toolchains/InProcess/Emit/InProcessEmitExecutor.cs:1
- Change coupling: Engine.cs ↔ EnginePilotStage.cs src/BenchmarkDotNet/Engines/Engine.cs:1
- Change coupling: DotNetCliExecutor.cs ↔ Executor.cs src/BenchmarkDotNet/Toolchains/DotNetCli/DotNetCliExecutor.cs:1
- Change coupling: EngineResolver.cs ↔ JobExtensions.cs src/BenchmarkDotNet/Engines/EngineResolver.cs:1
- Change coupling: Engine.cs ↔ EngineWarmupStage.cs src/BenchmarkDotNet/Engines/Engine.cs:1
- Duplicated block (8 lines × 2) src/BenchmarkDotNet.Analyzers/Attributes/GeneralParameterAttributesAnalyzer.cs:393
- Duplicated block (8 lines × 2) src/BenchmarkDotNet.Analyzers/AnalyzerHelper.cs:77
- Duplicated block (8 lines × 2) src/BenchmarkDotNet/Characteristics/CompositeResolver.cs:18
- Duplicated block (8 lines × 2) src/BenchmarkDotNet/Exporters/AsciiDocExporter.cs:47
- Duplicated block (8 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncEnumerableCoreEmitter.cs:213
- TooManyMethods: ManualConfig src/BenchmarkDotNet/Configs/ManualConfig.cs
- TooManyMethods: RunnableEmitter src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/RunnableEmitter.cs
- TooManyMethods: CharacteristicObject src/BenchmarkDotNet/Characteristics/CharacteristicObject.cs
- TooManyMethods: XxHashShared REDACTED
- Duplicated block (10 lines × 2) src/BenchmarkDotNet.Analyzers/Attributes/SetupCleanupAsyncEnumerableAnalyzer.cs:63
- Duplicated block (10 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/InProcessEmitRunner.cs:153
- Duplicated block (10 lines × 2) src/BenchmarkDotNet.Diagnostics.Windows/InliningDiagnoser.cs:76
- Duplicated block (10 lines × 2) src/BenchmarkDotNet/Parameters/DeepEqualityComparer.cs:18
- Duplicated block (15 lines × 2) src/BenchmarkDotNet/Toolchains/DotNetCli/DotNetCliExecutor.cs:100
- Duplicated block (15 lines × 2) src/BenchmarkDotNet.Analyzers/Attributes/BenchmarkCancellationAttributeAnalyzer.cs:68
- Duplicated block (15 lines × 2) src/BenchmarkDotNet/Disassemblers/Arm64Disassembler.cs:94
- Duplicated block (15 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/InProcessEmitRunner.cs:37
- Disposable acquired into a field and never released samples/BenchmarkDotNet.Samples/IntroFluentConfigBuilder.cs:16
- Disposable acquired into a field and never released samples/BenchmarkDotNet.Samples/IntroFluentConfigBuilder.cs:17
- Disposable acquired into a field and never released samples/BenchmarkDotNet.Samples/IntroStatisticsColumns.cs:12
- Disposable acquired into a field and never released samples/BenchmarkDotNet.Samples/IntroStatisticsColumns.cs:13
- No assertions: NullIsSupportedAsElementOfParamsSource tests/BenchmarkDotNet.Tests/ParamsSourceTests.cs:17
- No assertions: AllEnvRequirementsAreSupported tests/BenchmarkDotNet.Tests/XUnit/EnvRequirementCheckerTests.cs:6
- No assertions: InProcessBenchmarkRunsWithoutSaving tests/BenchmarkDotNet.IntegrationTests.RuntimeAsync/RuntimeAsyncEmitTest.cs:43
- ClassTooLong: BenchmarkRunnerClean src/BenchmarkDotNet/Running/BenchmarkRunnerClean.cs
- ClassTooLong: ConfigParser src/BenchmarkDotNet/ConsoleArguments/ConfigParser.cs
- ClassTooLong: AsyncEnumerableCoreEmitter src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncEnumerableCoreEmitter.cs
- Duplicated block (7 lines × 2) src/BenchmarkDotNet.Analyzers/General/BenchmarkClassAnalyzer.cs:355
- Duplicated block (7 lines × 2) build/BenchmarkDotNet.Build/Runners/ReleaseRunner.cs:29
- Duplicated block (7 lines × 2) src/BenchmarkDotNet/Validators/ExecutionValidator.cs:67
- Swallowed exception (caught, then discarded) src/BenchmarkDotNet/Extensions/PathFeatures.cs:89
- Swallowed exception (caught, then discarded) src/BenchmarkDotNet/Toolchains/CsProj/CsProjBuilder.cs:620
- Swallowed exception (caught, then discarded) src/BenchmarkDotNet/Validators/JitOptimizationsValidator.cs:25
- FileTooLong: Running/BenchmarkRunnerClean.cs src/BenchmarkDotNet/Running/BenchmarkRunnerClean.cs
- FileTooLong: REDACTED REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (26 corresponding lines) src/BenchmarkDotNet.Analyzers/AnalyzerHelper.cs:74
- Edited copy of a member (26 corresponding lines) src/BenchmarkDotNet/Helpers/CancelableStreamWriter.cs:208
- Edited copy of a member (6 corresponding lines) src/BenchmarkDotNet/Extensions/TaskExtensions.cs:22
- Edited copy of a member (6 corresponding lines) samples/BenchmarkDotNet.Samples/IntroHardwareCounters.cs:25
- Duplicated block (20 lines × 2) src/BenchmarkDotNet.Analyzers/Attributes/ArgumentsAttributeAnalyzer.cs:303
- Duplicated block (20 lines × 2) src/BenchmarkDotNet/Toolchains/DotNetCli/DotNetCliExecutor.cs:86
- Duplicated block (14 lines × 2) src/BenchmarkDotNet/Validators/ExecutionValidator.cs:51
- Duplicated block (14 lines × 2) src/BenchmarkDotNet/Disassemblers/Arm64Disassembler.cs:77
- Duplicated block (11 lines × 2) src/BenchmarkDotNet.Diagnostics.Windows/TailCallDiagnoser.cs:62
- Duplicated block (11 lines × 2) src/BenchmarkDotNet/Disassemblers/Arm64Disassembler.cs:273
- Duplicated block (7 lines × 3) src/BenchmarkDotNet/Toolchains/DotNetCli/DotNetCliExecutor.cs:100
- Duplicated block (7 lines × 3) src/BenchmarkDotNet.Diagnostics.Windows/TailCallDiagnoser.cs:48
- Duplicated block (9 lines × 2) src/BenchmarkDotNet.Diagnostics.dotMemory/DotMemoryDiagnoser.cs:70
- Duplicated block (9 lines × 2) samples/BenchmarkDotNet.Samples/IntroDisassembly.cs:23
- Duplicated block (5 lines × 2) src/BenchmarkDotNet/Disassemblers/Exporters/CombinedDisassemblyExporter.cs:40
- Duplicated block (5 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:137
- Duplicated block (7 lines × 5) src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/BenchmarkActionImpl.cs:43
- Duplicated block (7 lines × 5) src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/BenchmarkActionImpl.cs:53
- Fake-async — async method never awaits src/BenchmarkDotNet/Engines/NoAcknowledgementConsoleHost.cs:33
- Fake-async — async method never awaits src/BenchmarkDotNet/Extensions/XDocumentExtensions.cs:12
- Weak hash algorithm samples/BenchmarkDotNet.Samples/IntroFluentConfigBuilder.cs:16
- Weak hash algorithm samples/BenchmarkDotNet.Samples/IntroStatisticsColumns.cs:12
- Disposable created and abandoned in the method that made it src/BenchmarkDotNet.Exporters.Plotting/ScottPlotExporter.cs:181
- Disposable created and abandoned in the method that made it src/BenchmarkDotNet.Exporters.Plotting/ScottPlotExporter.cs:257
- No data-protection/encryption
- BenchmarkClassAnalyzer.AnalyzeClassDeclaration (cyclomatic 98) src/BenchmarkDotNet.Analyzers/General/BenchmarkClassAnalyzer.cs:112
- ArgumentsAttributeAnalyzer.AnalyzeMethodSymbol (cyclomatic 59) src/BenchmarkDotNet.Analyzers/Attributes/ArgumentsAttributeAnalyzer.cs:138
- LinuxCpuInfoParser.Parse (cyclomatic 38) src/BenchmarkDotNet/Detectors/Cpu/Linux/LinuxCpuInfoParser.cs:31
- Runtime.TryParse (cyclomatic 38) src/BenchmarkDotNet/Environments/Runtimes/Runtime.cs:85
- CsProjNativeAotBuilder.GetCurrentProcessInstructionSets (cyclomatic 38) src/BenchmarkDotNet/Toolchains/NativeAot/CsProjNativeAotBuilder.cs:155
- AsyncEnumerableCoreEmitter.EmitWorkloadCore (cyclomatic 35) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncEnumerableCoreEmitter.cs:49
- GeneralParameterAttributesAnalyzer.AnalyzeParamsSourceWriteOnlyProperty (cyclomatic 33) src/BenchmarkDotNet.Analyzers/Attributes/GeneralParameterAttributesAnalyzer.cs:348
- RunAnalyzer.Analyze (cyclomatic 32) src/BenchmarkDotNet.Analyzers/BenchmarkRunner/RunAnalyzer.cs:84
- IntelDisassembler.TryFollowJumpTrampoline (cyclomatic 32) src/BenchmarkDotNet/Disassemblers/IntelDisassembler.cs:242
- ConfigParser.Validate (cyclomatic 31) src/BenchmarkDotNet/ConsoleArguments/ConfigParser.cs:279
- Arm64RegisterValueAccumulator.Feed (cyclomatic 31) src/BenchmarkDotNet/Disassemblers/Arm64RegisterValueAccumulator.cs:40
- Arm64Disassembler.TryResolvePrecode (cyclomatic 29) src/BenchmarkDotNet/Disassemblers/Arm64Disassembler.cs:68
- IntelDisassembler.TryResolvePrecode (cyclomatic 28) src/BenchmarkDotNet/Disassemblers/IntelDisassembler.cs:79
- BaselineRatioColumn.GetValue (cyclomatic 25) src/BenchmarkDotNet/Columns/BaselineRatioColumn.cs:43
- ConfigParser.GetBaseJob (cyclomatic 25) src/BenchmarkDotNet/ConsoleArguments/ConfigParser.cs:506
- Arm64Disassembler.TryFollowJumpTrampoline (cyclomatic 25) src/BenchmarkDotNet/Disassemblers/Arm64Disassembler.cs:245
- ClrMdDisassembler.TryTranslateAddressToName (cyclomatic 24) src/BenchmarkDotNet/Disassemblers/ClrMdDisassembler.cs:269
- HardwareIntrinsics.GetFullInfo::GetCurrentProcessInstructionSets (cyclomatic 23) src/BenchmarkDotNet/Detectors/Cpu/HardwareIntrinsics.cs:51
- EngineJitStage.EnumerateIterations (cyclomatic 23) src/BenchmarkDotNet/Engines/EngineJitStage.cs:84
- AsyncBenchmarkAnalyzer.AnalyzeClassDeclaration (cyclomatic 22) src/BenchmarkDotNet.Analyzers/General/AsyncBenchmarkAnalyzer.cs:44
- JitListener.HandleMethodLoad (cyclomatic 22) src/BenchmarkDotNet/Engines/JitListener.cs:407
- SourceCodeHelper.IsCompilationTimeConstant (cyclomatic 22) src/BenchmarkDotNet/Helpers/SourceCodeHelper.cs:81
- RequiredMemberAnalyzer.Initialize (cyclomatic 21) src/BenchmarkDotNet.Analyzers/RequiredMemberAnalyzer.cs:43
- NativeMemoryLogParser.Parse (cyclomatic 21) src/BenchmarkDotNet.Diagnostics.Windows/Tracing/NativeMemoryLogParser.cs:65
- CpuInfoParser.ParseCore (cyclomatic 21) src/BenchmarkDotNet/Detectors/Cpu/Windows/CpuInfoParser.cs:28
- NumericStringComparer.Compare (cyclomatic 21) src/BenchmarkDotNet/Jobs/JobComparer.cs:133
- ConfigParser.CreateConfig (cyclomatic 20) src/BenchmarkDotNet/ConsoleArguments/ConfigParser.cs:429
- DeepEqualityComparer.ValuesEqual (cyclomatic 20) src/BenchmarkDotNet/Parameters/DeepEqualityComparer.cs:36
- BenchmarkRunnerClean.Execute (cyclomatic 20) src/BenchmarkDotNet/Running/BenchmarkRunnerClean.cs:523
- BenchmarkActionFactory.CreateCore (cyclomatic 20) src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/BenchmarkActionFactory.cs:10
- DisassemblyDiagnoser.ValidateAsync (cyclomatic 19) src/BenchmarkDotNet/Disassemblers/DisassemblyDiagnoser.cs:121
- Engine.RunCore (cyclomatic 19) src/BenchmarkDotNet/Engines/Engine.cs:93
- SystemMemory.ParseMacMemoryJson (cyclomatic 19) src/BenchmarkDotNet/Environments/PhysicalMemoryInfo.cs:393
- BenchmarkRunnerClean.Run (cyclomatic 19) src/BenchmarkDotNet/Running/BenchmarkRunnerClean.cs:208
- ArgumentsSourceElementTypeCodeFixProvider.Plan (cyclomatic 18) src/BenchmarkDotNet.CodeFixers/ArgumentsSourceElementTypeCodeFixProvider.cs:58
- LinuxOsReleaseHelper.GetNameByOsRelease (cyclomatic 18) src/BenchmarkDotNet/Helpers/LinuxOsReleaseHelper.cs:7
- InProcessNoEmitRunner.FillMembers (cyclomatic 18) src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/InProcessNoEmitRunner.cs:72
- Broker.ProcessDataCore (cyclomatic 17) src/BenchmarkDotNet/Loggers/Broker.cs:70
- NumeralSystemExtensions.ToRoman (cyclomatic 17) src/BenchmarkDotNet/Mathematics/NumeralSystemExtensions.cs:21
- BenchmarkRunnerClean.Run (cyclomatic 17) src/BenchmarkDotNet/Running/BenchmarkRunnerClean.cs:39
- CommandLineParser.Parse (cyclomatic 17) build/BenchmarkDotNet.Build/CommandLineParser.cs:20
- ParamsAttributeAnalyzer.Analyze (cyclomatic 16) src/BenchmarkDotNet.Analyzers/Attributes/ParamsAttributeAnalyzer.cs:61
- DisassemblyPrettifier.Prettify (cyclomatic 16) src/BenchmarkDotNet/Disassemblers/Exporters/DisassemblyPrettifier.cs:33
- CancelableStreamReader.DetectEncoding (cyclomatic 16) src/BenchmarkDotNet/Helpers/CancelableStreamReader.cs:319
- BareSuppressMessage repeated across 21 files src/BenchmarkDotNet.Diagnostics.Windows/Tracing/NativeMemoryLogParser.cs:17
- HackComment src/BenchmarkDotNet/Toolchains/InProcess/Emit/InProcessEmitBuilder.cs:20
- DeadPreprocessorBranch tests/BenchmarkDotNet.IntegrationTests.ManualRunning/MsBuildArgumentTests.cs:83
- TodoComment repeated across 15 files tests/BenchmarkDotNet.Tests/Disassemblers/Arm64/Arm64DisassemblerTests.Decode.cs:1
- BenchmarkClassAnalyzer.AnalyzeClassDeclaration (cognitive 499) src/BenchmarkDotNet.Analyzers/General/BenchmarkClassAnalyzer.cs:112
- ArgumentsAttributeAnalyzer.AnalyzeMethodSymbol (cognitive 78) src/BenchmarkDotNet.Analyzers/Attributes/ArgumentsAttributeAnalyzer.cs:138
- CsProjNativeAotBuilder.GetCurrentProcessInstructionSets (cognitive 68) src/BenchmarkDotNet/Toolchains/NativeAot/CsProjNativeAotBuilder.cs:155
- LinuxCpuInfoParser.Parse (cognitive 53) src/BenchmarkDotNet/Detectors/Cpu/Linux/LinuxCpuInfoParser.cs:31
- EngineJitStage.EnumerateIterations (cognitive 51) src/BenchmarkDotNet/Engines/EngineJitStage.cs:84
- AsyncBenchmarkAnalyzer.AnalyzeClassDeclaration (cognitive 49) src/BenchmarkDotNet.Analyzers/General/AsyncBenchmarkAnalyzer.cs:44
- RunAnalyzer.Analyze (cognitive 48) src/BenchmarkDotNet.Analyzers/BenchmarkRunner/RunAnalyzer.cs:84
- BaselineRatioColumn.GetValue (cognitive 47) src/BenchmarkDotNet/Columns/BaselineRatioColumn.cs:43
- ConfigParser.Validate (cognitive 46) src/BenchmarkDotNet/ConsoleArguments/ConfigParser.cs:279
- AsyncEnumerableCoreEmitter.EmitWorkloadCore (cognitive 46) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncEnumerableCoreEmitter.cs:49
- Runtime.TryParse (cognitive 41) src/BenchmarkDotNet/Environments/Runtimes/Runtime.cs:85
- HardwareIntrinsics.GetFullInfo::GetCurrentProcessInstructionSets (cognitive 39) src/BenchmarkDotNet/Detectors/Cpu/HardwareIntrinsics.cs:51
- DisassemblyPrettifier.Prettify (cognitive 39) src/BenchmarkDotNet/Disassemblers/Exporters/DisassemblyPrettifier.cs:33
- BenchmarkRunnerClean.Run (cognitive 39) src/BenchmarkDotNet/Running/BenchmarkRunnerClean.cs:208
- ClrMdDisassembler.TryTranslateAddressToName (cognitive 38) src/BenchmarkDotNet/Disassemblers/ClrMdDisassembler.cs:269
- ReturnValueValidator.ValidateAsyncCore (cognitive 37) src/BenchmarkDotNet/Validators/ReturnValueValidator.cs:18
- Engine.RunCore (cognitive 35) src/BenchmarkDotNet/Engines/Engine.cs:93
- InstructionPointerExporter.ExportAsync (cognitive 35) src/BenchmarkDotNet/Exporters/InstructionPointerExporter.cs:164
- GeneralParameterAttributesAnalyzer.AnalyzeParamsSourceWriteOnlyProperty (cognitive 34) src/BenchmarkDotNet.Analyzers/Attributes/GeneralParameterAttributesAnalyzer.cs:348
- WeaveAssemblyTask.Execute (cognitive 33) src/BenchmarkDotNet.Weaver/src/WeaveAssemblyTask.cs:62
- InstructionPointerExporter.SumHardwareCountersPerMethod (cognitive 33) src/BenchmarkDotNet/Exporters/InstructionPointerExporter.cs:104
- Broker.ProcessDataCore (cognitive 33) src/BenchmarkDotNet/Loggers/Broker.cs:70
- NumericStringComparer.Compare (cognitive 32) src/BenchmarkDotNet/Jobs/JobComparer.cs:133
- InProcessNoEmitRunner.FillMembers (cognitive 32) src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/InProcessNoEmitRunner.cs:72
- Arm64RegisterValueAccumulator.Feed (cognitive 31) src/BenchmarkDotNet/Disassemblers/Arm64RegisterValueAccumulator.cs:40
- ClrMdDisassembler.FilterAndEnqueue (cognitive 30) src/BenchmarkDotNet/Disassemblers/ClrMdDisassembler.cs:121
- BenchmarkActionFactory.CreateCore (cognitive 30) src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/BenchmarkActionFactory.cs:10
- RequiredMemberAnalyzer.Initialize (cognitive 29) src/BenchmarkDotNet.Analyzers/RequiredMemberAnalyzer.cs:43
- ArgumentsSourceElementTypeCodeFixProvider.Plan (cognitive 28) src/BenchmarkDotNet.CodeFixers/ArgumentsSourceElementTypeCodeFixProvider.cs:58
- RuntimeInformation.GetRuntimeVersion (cognitive 28) src/BenchmarkDotNet/Portability/RuntimeInformation.cs:99
- ConfigParser.Expand (cognitive 27) src/BenchmarkDotNet/ConsoleArguments/ConfigParser.cs:572
- DisassemblyDiagnoser.ValidateAsync (cognitive 27) src/BenchmarkDotNet/Disassemblers/DisassemblyDiagnoser.cs:121
- CancelableStreamReader.ReadLineAsync (cognitive 27) src/BenchmarkDotNet/Helpers/CancelableStreamReader.cs:129
- DeepEqualityComparer.ValuesEqual (cognitive 27) src/BenchmarkDotNet/Parameters/DeepEqualityComparer.cs:36
- BenchmarkRunnerClean.Execute (cognitive 27) src/BenchmarkDotNet/Running/BenchmarkRunnerClean.cs:523
- ParamsValidator.ValidateAsync (cognitive 27) src/BenchmarkDotNet/Validators/ParamsValidator.cs:27
- BenchmarkCancellationValidator.ValidateAsync (cognitive 26) src/BenchmarkDotNet/Validators/BenchmarkCancellationValidator.cs:19
- AsyncBenchmarkCodeFixProvider.AddCancellationTokenPropertyAsync (cognitive 24) src/BenchmarkDotNet.CodeFixers/AsyncBenchmarkCodeFixProvider.cs:48
- ConfigParser.GetBaseJob (cognitive 24) src/BenchmarkDotNet/ConsoleArguments/ConfigParser.cs:506
- SystemMemory.ParseSmbiosMemoryDevices (cognitive 24) src/BenchmarkDotNet/Environments/PhysicalMemoryInfo.cs:264
- CpuInfoParser.ParseCore (cognitive 23) src/BenchmarkDotNet/Detectors/Cpu/Windows/CpuInfoParser.cs:28
- BuildContext.BuildContext.ctor (cognitive 23) build/BenchmarkDotNet.Build/BuildContext.cs:57
- GeneralParameterAttributesAnalyzer.AnalyzeFieldOrPropertySymbol (cognitive 22) src/BenchmarkDotNet.Analyzers/Attributes/GeneralParameterAttributesAnalyzer.cs:232
- ImmutableConfigBuilder.GetExporters (cognitive 22) src/BenchmarkDotNet/Configs/ImmutableConfigBuilder.cs:106
- HtmlDisassemblyExporter.Export (cognitive 22) src/BenchmarkDotNet/Disassemblers/Exporters/HtmlDisassemblyExporter.cs:49
- JitListener.HandleMethodLoad (cognitive 22) src/BenchmarkDotNet/Engines/JitListener.cs:407
- BenchmarkRunnerClean.Run (cognitive 22) src/BenchmarkDotNet/Running/BenchmarkRunnerClean.cs:39
- InProcessEmitRunner.FillMembers (cognitive 22) src/BenchmarkDotNet/Toolchains/InProcess/Emit/InProcessEmitRunner.cs:130
- NativeMemoryLogParser.Parse (cognitive 21) src/BenchmarkDotNet.Diagnostics.Windows/Tracing/NativeMemoryLogParser.cs:65
- Arm64Disassembler.TryResolvePrecode (cognitive 21) src/BenchmarkDotNet/Disassemblers/Arm64Disassembler.cs:68
- IntelDisassembler.TryFollowJumpTrampoline (cognitive 21) src/BenchmarkDotNet/Disassemblers/IntelDisassembler.cs:242
- SystemMemory.GetLinuxMemoryDetails (cognitive 21) src/BenchmarkDotNet/Environments/PhysicalMemoryInfo.cs:171
- SourceCodeHelper.IsCompilationTimeConstant (cognitive 21) src/BenchmarkDotNet/Helpers/SourceCodeHelper.cs:81
- SetupCleanupValidator.ValidateAttributes (cognitive 21) src/BenchmarkDotNet/Validators/SetupCleanupValidator.cs:56
- ConfigParser.ConsumeTokens (cognitive 20) src/BenchmarkDotNet/ConsoleArguments/ConfigParser.cs:181
- ConfigParser.CreateConfig (cognitive 20) src/BenchmarkDotNet/ConsoleArguments/ConfigParser.cs:429
- Arm64Disassembler.TryFollowJumpTrampoline (cognitive 20) src/BenchmarkDotNet/Disassemblers/Arm64Disassembler.cs:245
- CancelableStreamReader.ReadBufferAsync (cognitive 19) src/BenchmarkDotNet/Helpers/CancelableStreamReader.cs:208
- JobComparer.Compare (cognitive 19) src/BenchmarkDotNet/Jobs/JobComparer.cs:34
- BaselineAllocationRatioColumn.GetValue (cognitive 18) src/BenchmarkDotNet/Columns/BaselineAllocationRatioColumn.cs:18
- ClrMdDisassembler.DisassembleMethod (cognitive 18) src/BenchmarkDotNet/Disassemblers/ClrMdDisassembler.cs:174
- EngineStage.EnumerateStages (cognitive 18) src/BenchmarkDotNet/Engines/EngineStage.cs:19
- SystemMemory.ParseMacMemoryJson (cognitive 18) src/BenchmarkDotNet/Environments/PhysicalMemoryInfo.cs:393
- MarkdownExporter.PrintTableAsync (cognitive 18) src/BenchmarkDotNet/Exporters/MarkdownExporter.cs:137
- LinuxOsReleaseHelper.GetNameByOsRelease (cognitive 18) src/BenchmarkDotNet/Helpers/LinuxOsReleaseHelper.cs:7
- ProcessHelper.TryResolveExecutableInPath (cognitive 18) src/BenchmarkDotNet/Helpers/ProcessHelper.cs:191
- CommandLineParser.Parse (cognitive 18) build/BenchmarkDotNet.Build/CommandLineParser.cs:20
- RequiredMemberAnalyzer.GetBaseTypeReferenceLocation (cognitive 17) src/BenchmarkDotNet.Analyzers/RequiredMemberAnalyzer.cs:169
- DeepEqualityComparer.TryFallbackStructuralEquals (cognitive 17) src/BenchmarkDotNet/Parameters/DeepEqualityComparer.cs:152
- ParameterComparer.TryFallbackStructuralCompareTo (cognitive 17) src/BenchmarkDotNet/Parameters/ParameterComparer.cs:92
- TypeFilter.GetTypesWithRunnableBenchmarks (cognitive 17) src/BenchmarkDotNet/Running/TypeFilter.cs:12
- CombinedDisassemblyExporter.PrintTableAsync (cognitive 16) src/BenchmarkDotNet/Disassemblers/Exporters/CombinedDisassemblyExporter.cs:76
- GithubMarkdownDisassemblyExporter.ExportAsync (cognitive 16) src/BenchmarkDotNet/Disassemblers/Exporters/GithubMarkdownDisassemblyExporter.cs:35
- IntelDisassembler.Decode (cognitive 16) src/BenchmarkDotNet/Disassemblers/IntelDisassembler.cs:10
- IntelDisassembler.TryResolvePrecode (cognitive 16) src/BenchmarkDotNet/Disassemblers/IntelDisassembler.cs:79
- ProcessExtensions.SetCoreRunEnvironmentVariables (cognitive 16) src/BenchmarkDotNet/Extensions/ProcessExtensions.cs:237
- ReflectionExtensions.GetCorrectCSharpTypeName (cognitive 16) src/BenchmarkDotNet/Extensions/ReflectionExtensions.cs:39
- NumeralSystemExtensions.ToRoman (cognitive 16) src/BenchmarkDotNet/Mathematics/NumeralSystemExtensions.cs:21
- MsBuildErrorMapper.TryToExplainMissingReference (cognitive 16) src/BenchmarkDotNet/Toolchains/DotNetCli/MsBuildErrorMapper.cs:72
- Change-coupling hub: WasmRuntime.cs → CommandLineOptions.cs, ConfigParser.cs, CsProjWasmBuilder.cs src/BenchmarkDotNet/Environments/Runtimes/WasmRuntime.cs
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (44 corresponding lines) src/BenchmarkDotNet/Toolchains/InProcess/Emit/InProcessEmitExecutor.cs:17
- Edited copy of a member (27 corresponding lines) src/BenchmarkDotNet/Toolchains/InProcess/Emit/InProcessEmitRunner.cs:18
- Members sharing a duplicated core (6 members, 50+ identical tokens) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:72
- Edited copy of a member (74 corresponding lines) src/BenchmarkDotNet.Exporters.Plotting/ScottPlotExporter.cs:180
- Edited copy of a member (49 corresponding lines) src/BenchmarkDotNet.Diagnostics.Windows/InliningDiagnoser.cs:48
- Edited copy of a member (69 corresponding lines) src/BenchmarkDotNet/Parameters/DeepEqualityComparer.cs:153
- Edited copy of a member (38 corresponding lines) REDACTED:689
- Edited copy of a member (52 corresponding lines) src/BenchmarkDotNet.Analyzers/Attributes/SetupCleanupAsyncEnumerableAnalyzer.cs:77
- Edited copy of a member (45 corresponding lines) src/BenchmarkDotNet.Analyzers/Attributes/BenchmarkCancellationAttributeAnalyzer.cs:132
- Edited copy of a member (31 corresponding lines) src/BenchmarkDotNet.Analyzers/Attributes/SetupCleanupAsyncEnumerableAnalyzer.cs:41
- Edited copy of a member (20 corresponding lines) src/BenchmarkDotNet/Engines/GcStats.cs:249
- Edited copies of one member (4 members, 7+ corresponding lines) src/BenchmarkDotNet/Extensions/TaskExtensions.cs:38
- Edited copy of a member (25 corresponding lines) src/BenchmarkDotNet.Analyzers/AnalyzerHelper.cs:190
- Edited copies of one member (4 members, 16+ corresponding lines) src/BenchmarkDotNet.Analyzers/Attributes/ArgumentsAttributeAnalyzer.cs:121
- Edited copy of a member (15 corresponding lines) src/BenchmarkDotNet.Analyzers/Attributes/ParamsAttributeAnalyzer.cs:44
- Edited copy of a member (7 corresponding lines) src/BenchmarkDotNet.Diagnostics.dotMemory/DotMemoryDiagnoser.cs:25
- Duplicated block (26–65 lines × 5) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:142
- Duplicated block (54 lines × 2) src/BenchmarkDotNet.Exporters.Plotting/ScottPlotExporter.cs:181
- Duplicated block (44–51 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/SyncCoreEmitter.cs:33
- Duplicated block (36 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/InProcessEmitExecutor.cs:20
- Duplicated block (32–38 lines × 2) src/BenchmarkDotNet.Analyzers/Attributes/SetupCleanupAsyncEnumerableAnalyzer.cs:77
- Duplicated block (32 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/InProcessEmitExecutor.cs:65
- Duplicated block (22–32 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitterBase.cs:245
- Duplicated block (10–31 lines × 6) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:163
- Duplicated block (16–30 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:99
- Duplicated block (21–28 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:343
- Duplicated block (27 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/BenchmarkActionImpl.cs:596
- Duplicated block (26 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/BenchmarkActionImpl.cs:368
- Duplicated block (12–26 lines × 7) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:142
- Duplicated block (22 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/InProcessEmitRunner.cs:76
- Duplicated block (24 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/BenchmarkActionImpl.cs:294
- Duplicated block (10–24 lines × 6) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:161
- Duplicated block (19–24 lines × 2) src/BenchmarkDotNet/Disassemblers/IntelDisassembler.cs:94
- Duplicated block (22–23 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:178
- Duplicated block (21 lines × 2) src/BenchmarkDotNet/Reports/SummaryTableExtensions.cs:77
- Duplicated block (18 lines × 2) src/BenchmarkDotNet.Diagnostics.dotMemory/DotMemoryDiagnoser.cs:51
- Duplicated block (12–19 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/SyncCoreEmitter.cs:83
- Duplicated block (17–18 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/SyncCoreEmitter.cs:143
- Duplicated block (11–17 lines × 3) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitterBase.cs:215
- Duplicated block (17 lines × 2) src/BenchmarkDotNet.Analyzers/Attributes/ArgumentsAttributeAnalyzer.cs:459
- Duplicated block (16 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:270
- Duplicated block (14 lines × 3) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:272
- Duplicated block (8–13 lines × 2) src/BenchmarkDotNet/Helpers/DynamicAwaitHelper.cs:53
- Duplicated block (3–11 lines × 3) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:289
- Duplicated block (9–10 lines × 4) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncEnumerableCoreEmitter.cs:328
- Duplicated block (8 lines × 7) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:163
- Duplicated block (7–8 lines × 2) src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:127
- Duplicated block (6–7 lines × 2) src/BenchmarkDotNet/Disassemblers/IntelDisassembler.cs:291
- Duplicated block (10 lines × 4) src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/BenchmarkActionImpl.cs:739
- Duplicated block (7 lines × 4) src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/BenchmarkActionImpl.cs:752
- Edited copy of a member (9 corresponding lines) samples/BenchmarkDotNet.Samples/IntroDisassembly.cs:13
- Unstable project BenchmarkDotNet.CodeFixers src/BenchmarkDotNet.CodeFixers/BenchmarkDotNet.CodeFixers.csproj:1
- Unstable project BenchmarkDotNet.Diagnostics.Windows src/BenchmarkDotNet.Diagnostics.Windows/BenchmarkDotNet.Diagnostics.Windows.csproj:1
- Unstable project BenchmarkDotNet.Exporters.Plotting src/BenchmarkDotNet.Exporters.Plotting/BenchmarkDotNet.Exporters.Plotting.csproj:1
- Off the main sequence: BenchmarkDotNet(netstandard2.0) src/BenchmarkDotNet/BenchmarkDotNet.csproj:1
- Empty method body — does nothing with its inputs src/BenchmarkDotNet/Engines/Engine.cs:263
- Guard cannot change the result — returns what the code already falls through to src/BenchmarkDotNet/Helpers/SourceCodeHelper.cs:113
- Condition was already decided — an earlier guard makes this test constant src/BenchmarkDotNet/Jobs/JobComparer.cs:66
- Coverage collected but not gated
- Outbound HTTP without resilience build/BenchmarkDotNet.Build/Meta/Repo.cs:24
- NuGet dependencies are not locked
- Blocking `Engine.SleepIfPositive` inside an `async` method src/BenchmarkDotNet/Engines/Engine.cs:213
- Blocking `Thread.Sleep` inside an `async` method src/BenchmarkDotNet/Engines/TcpHost.cs:83
- Sync-over-async (deadlock risk) through `.Wait(…)` src/BenchmarkDotNet/Helpers/ProcessHelper.cs:56
- Disposes a dependency it does not own src/BenchmarkDotNet/Loggers/TextLogger.cs:20
- Async local function without CancellationToken: Cancel src/BenchmarkDotNet/Loggers/Broker.cs:92
- Async call defeats the CancellationToken: ProcessDataCore src/BenchmarkDotNet/Loggers/Broker.cs:94
- Symbol treated as nullable, then dereferenced unguarded src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/BenchmarkActionFactory.cs:113
Minor — 146 finding(s)
- Commented-out code src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:126
- Commented-out code src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:132
- Commented-out code src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:136
- Commented-out code src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:155
- Commented-out code src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:167
- Commented-out code src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:176
- Commented-out code src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:179
- Commented-out code src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:181
- Commented-out code src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:187
- Commented-out code src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:195
- Commented-out code src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:216
- Commented-out code src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:236
- Commented-out code src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:248
- Commented-out code src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:288
- Commented-out code src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:297
- Commented-out code src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:301
- Commented-out code src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:320
- Commented-out code src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:332
- Commented-out code src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:341
- Commented-out code src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:344
- Commented-out code src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:347
- Commented-out code src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:361
- Commented-out code src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:367
- Commented-out code src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:369
- Commented-out code src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:378
- Public type used only inside its own library src/BenchmarkDotNet.Diagnostics.Windows/ConcurrencyVisualizerProfiler.cs:23
- Public type used only inside its own library src/BenchmarkDotNet.Diagnostics.Windows/EtwProfiler.cs:17
- Public type used only inside its own library src/BenchmarkDotNet.Diagnostics.Windows/HardwareCounters.cs:9
- Public type used only inside its own library src/BenchmarkDotNet.Diagnostics.Windows/InliningDiagnoser.cs:8
- Public type used only inside its own library src/BenchmarkDotNet.Diagnostics.Windows/JitStatsDiagnoser.cs:11
- Public type used only inside its own library src/BenchmarkDotNet.Diagnostics.Windows/NativeMemoryProfiler.cs:15
- Public type used only inside its own library src/BenchmarkDotNet.Diagnostics.Windows/TailCallDiagnoser.cs:12
- Public type used only inside its own library src/BenchmarkDotNet.Diagnostics.Windows/Tracing/EngineEventLogParser.cs:8
- Public type used only inside its own library src/BenchmarkDotNet.Diagnostics.Windows/Tracing/NativeMemoryLogParser.cs:17
- Public type used only inside its own library src/BenchmarkDotNet.Diagnostics.Windows/Tracing/TraceLogParser.cs:11
- Public type used only inside its own library src/BenchmarkDotNet.Diagnostics.Windows/Tracing/TraceLogParser.cs:91
- Public type used only inside its own library src/BenchmarkDotNet.Diagnostics.Windows/Tracing/TraceLogParser.cs:218
- Public type used only inside its own library src/BenchmarkDotNet/Analysers/BaselineCustomAnalyzer.cs:7
- Public type used only inside its own library src/BenchmarkDotNet/Analysers/BaselineCustomAnalyzer.cs:7
- Public type used only inside its own library src/BenchmarkDotNet/Analysers/BaselineCustomAnalyzer.cs:7
- Public type used only inside its own library src/BenchmarkDotNet/Analysers/CompositeAnalyser.cs:6
- Public type used only inside its own library src/BenchmarkDotNet/Analysers/CompositeAnalyser.cs:6
- Public type used only inside its own library src/BenchmarkDotNet/Analysers/CompositeAnalyser.cs:6
- Public type used only inside its own library src/BenchmarkDotNet/Analysers/ConclusionHelper.cs:5
- Public type used only inside its own library src/BenchmarkDotNet/Analysers/ConclusionHelper.cs:5
- Public type used only inside its own library src/BenchmarkDotNet/Analysers/EnvironmentAnalyser.cs:11
- Public type used only inside its own library src/BenchmarkDotNet/Analysers/HideColumnsAnalyser.cs:6
- Public type used only inside its own library src/BenchmarkDotNet/Analysers/HideColumnsAnalyser.cs:6
- Public type used only inside its own library src/BenchmarkDotNet/Analysers/HideColumnsAnalyser.cs:6
- Public type used only inside its own library src/BenchmarkDotNet/Analysers/MinIterationTimeAnalyser.cs:8
- Silent fallback default in catch src/BenchmarkDotNet/ConsoleArguments/ConfigParser.cs:686
- Silent fallback default in catch src/BenchmarkDotNet/Detectors/Cpu/Windows/DefaultCpuDetector.cs:28
- Silent fallback default in catch src/BenchmarkDotNet/Detectors/OsDetector.cs:87
- Silent fallback default in catch src/BenchmarkDotNet/Detectors/OsDetector.cs:114
- Silent fallback default in catch src/BenchmarkDotNet/Engines/GcStats.cs:264
- Silent fallback default in catch src/BenchmarkDotNet/Engines/GcStats.cs:286
- Silent fallback default in catch src/BenchmarkDotNet/Engines/GcStats.cs:307
- Silent fallback default in catch src/BenchmarkDotNet/Engines/JitListener.cs:517
- Silent fallback default in catch src/BenchmarkDotNet/Extensions/AssemblyExtensions.cs:24
- Silent fallback default in catch src/BenchmarkDotNet/Extensions/PathFeatures.cs:89
- Silent fallback default in catch src/BenchmarkDotNet/Helpers/FileCleanupHelper.cs:66
- Silent fallback default in catch src/BenchmarkDotNet/Helpers/FileCleanupHelper.cs:80
- Silent fallback default in catch src/BenchmarkDotNet/Helpers/LinuxOsReleaseHelper.cs:56
- Silent fallback default in catch src/BenchmarkDotNet/Helpers/ProcessHelper.cs:42
- Silent fallback default in catch src/BenchmarkDotNet/Helpers/ProcessHelper.cs:185
- Silent fallback default in catch src/BenchmarkDotNet/Helpers/TaskbarProgress.cs:124
- Silent fallback default in catch src/BenchmarkDotNet/Portability/RuntimeInformation.cs:77
- Silent fallback default in catch src/BenchmarkDotNet/Portability/RuntimeInformation.cs:293
- Silent fallback default in catch src/BenchmarkDotNet/Portability/RuntimeInformation.cs:314
- Silent fallback default in catch src/BenchmarkDotNet/Toolchains/CoreRun/CoreRunToolchain.cs:117
- Silent fallback default in catch src/BenchmarkDotNet/Toolchains/CsProj/CsProjBuilder.cs:635
- Silent fallback default in catch src/BenchmarkDotNet/Toolchains/DotNetCli/DotNetCliCommandExecutor.cs:102
- Silent fallback default in catch src/BenchmarkDotNet/Validators/DotNetSdkValidator.cs:113
- Silent fallback default in catch src/BenchmarkDotNet/Validators/JitOptimizationsValidator.cs:25
- redundant comment src/BenchmarkDotNet.Analyzers/AnalyzerHelper.cs:373
- redundant comment src/BenchmarkDotNet.Analyzers/General/AsyncBenchmarkAnalyzer.cs:88
- redundant comment src/BenchmarkDotNet.CodeFixers/AsyncBenchmarkCodeFixProvider.cs:29
- redundant comment src/BenchmarkDotNet.CodeFixers/AsyncBenchmarkCodeFixProvider.cs:39
- redundant comment src/BenchmarkDotNet.CodeFixers/AsyncBenchmarkCodeFixProvider.cs:124
- redundant comment src/BenchmarkDotNet.CodeFixers/AsyncBenchmarkCodeFixProvider.cs:148
- redundant comment src/BenchmarkDotNet.Diagnostics.Windows/Sessions.cs:44
- redundant comment src/BenchmarkDotNet.TestAdapter/VSTestAdapter.cs:114
- redundant comment src/BenchmarkDotNet/Disassemblers/DataContracts.cs:176
- redundant comment src/BenchmarkDotNet/Engines/FileStdOutConnection.cs:17
- redundant comment src/BenchmarkDotNet/Engines/GcStats.cs:300
- redundant comment src/BenchmarkDotNet/Helpers/FrameworkVersionHelper.cs:114
- redundant comment src/BenchmarkDotNet/Portability/RuntimeInformation.cs:93
- redundant comment tests/BenchmarkDotNet.Exporters.Plotting.Tests/ScottPlotExporterTests.cs:241
- redundant comment tests/BenchmarkDotNet.IntegrationTests/DisassemblyDiagnoserTests.cs:52
- redundant comment tests/BenchmarkDotNet.IntegrationTests/DisassemblyDiagnoserTests.cs:57
- redundant comment tests/BenchmarkDotNet.IntegrationTests/RunningEmptyBenchmarkTests.cs:258
- redundant comment tests/BenchmarkDotNet.IntegrationTests/RunningEmptyBenchmarkTests.cs:290
- redundant comment tests/BenchmarkDotNet.IntegrationTests/RunningEmptyBenchmarkTests.cs:330
- redundant comment tests/BenchmarkDotNet.Tests/Configs/JobTests.cs:404
- redundant comment tests/BenchmarkDotNet.Tests/Disassemblers/Arm64/Arm64DisassemblerTests.Decode.cs:16
- redundant comment tests/BenchmarkDotNet.Tests/Exporters/MarkdownExporterVerifyTests.cs:210
- Duplicated predicate src/BenchmarkDotNet/Parameters/DeepEqualityComparer.cs:174
- Duplicated predicate src/BenchmarkDotNet.Diagnostics.dotMemory/DotMemoryDiagnoser.cs:75
- Duplicated predicate src/BenchmarkDotNet/Toolchains/Mono/RoslynMonoAotToolchain.cs:39
- Duplicated predicate src/BenchmarkDotNet/Engines/TcpHost.cs:92
- Duplicated predicate src/BenchmarkDotNet/Engines/TcpHost.cs:93
- Duplicated predicate src/BenchmarkDotNet.Analyzers/Attributes/ArgumentsAttributeAnalyzer.cs:149
- Duplicated predicate src/BenchmarkDotNet.Analyzers/BenchmarkRunner/RunAnalyzer.cs:195
- Duplicated predicate src/BenchmarkDotNet/Helpers/DynamicAwaitHelper.cs:56
- Duplicated predicate src/BenchmarkDotNet/Code/CodeGenerator.cs:329
- Duplicated predicate src/BenchmarkDotNet/Disassemblers/Arm64Disassembler.cs:301
- Duplicated predicate src/BenchmarkDotNet/Toolchains/InProcess/Emit/InProcessEmitExecutor.cs:42
- Duplicated predicate src/BenchmarkDotNet/Toolchains/InProcess/Emit/Implementation/Emitters/AsyncCoreEmitter.cs:21
- Duplicated predicate src/BenchmarkDotNet/Validators/BenchmarkCancellationValidator.cs:56
- Duplicated predicate src/BenchmarkDotNet/Disassemblers/Arm64Disassembler.cs:130
- Duplicated predicate src/BenchmarkDotNet/Disassemblers/Arm64Disassembler.cs:80
- Duplicated predicate src/BenchmarkDotNet.Analyzers/Attributes/ArgumentsAttributeAnalyzer.cs:314
- Duplicated predicate src/BenchmarkDotNet.Analyzers/Attributes/ArgumentsAttributeAnalyzer.cs:462
- Pass-through layer src/BenchmarkDotNet/Exporters/Xml/SimpleXmlWriter.cs:5
- Pass-through layer src/BenchmarkDotNet/Loggers/TextLogger.cs:3
- Pass-through layer src/BenchmarkDotNet/Helpers/CancelableStreamReader.cs:8
- Member throws NotSupportedException src/BenchmarkDotNet/ConsoleArguments/ListBenchmarks/BenchmarkCaseJsonConverter.cs:57
- Member throws NotSupportedException src/BenchmarkDotNet/Helpers/HashCode.cs:146
- Member throws NotSupportedException src/BenchmarkDotNet/Helpers/HashCode.cs:151
- Silent fallback default on parse failure src/BenchmarkDotNet/Portability/JitInfo.cs:203
- Silent fallback default on parse failure src/BenchmarkDotNet/Reports/Measurement.cs:66
- Silent fallback default on parse failure src/BenchmarkDotNet/Reports/Measurement.cs:68
- Fat interface: IConfig (23 members) src/BenchmarkDotNet/Configs/IConfig.cs:17
- Partial data-retention evidence
- ObsoleteWithoutCallers src/BenchmarkDotNet/Helpers/CodeAnnotations.cs:864
- Thin analysable surface across projects: BenchmarkDotNet.IntegrationTests.CustomPaths tests/BenchmarkDotNet.IntegrationTests.CustomPaths/BenchmarkDotNet.IntegrationTests.CustomPaths.csproj
- Projects may be oversized for their cohesion src/BenchmarkDotNet/BenchmarkDotNet.csproj:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Sleep-based test synchronization
- No dependency-update automation build/BenchmarkDotNet.Build/BenchmarkDotNet.Build.csproj:10
- Not all async methods take a CancellationToken
- Some async methods drop the CancellationToken they accept
- Null-forgiving operator (`!`) suppressions override nullable warnings
Minor — 14 finding(s)
- Skipped (documented): UserCanSpecifyWasmArgs tests/BenchmarkDotNet.Tests/ConfigParserTests.cs:1103
- Skipped (documented): AdrpThenAdd_WithShiftedImm_ShouldCalculateAddress tests/BenchmarkDotNet.Tests/Disassemblers/Arm64/Arm64RegisterValueAccumulatorTests.AdrpThenAdd.cs:76
- Skipped (documented): AdrpThenOther_ThenAdd_ShouldResetValue tests/BenchmarkDotNet.Tests/Disassemblers/Arm64/Arm64RegisterValueAccumulatorTests.AdrpThenAdd.cs:117
- Skipped (documented): Movz_WithShiftedImmediateValue_ShouldStartNewValue tests/BenchmarkDotNet.Tests/Disassemblers/Arm64/Arm64RegisterValueAccumulatorTests.Movz.cs:12
- Skipped (documented): MovzThenMovk_WithSameShiftValue_ShouldHasAccumulatedValue tests/BenchmarkDotNet.Tests/Disassemblers/Arm64/Arm64RegisterValueAccumulatorTests.MovzThenMovk.cs:52
- Skipped (documented): MovzThenRet_ShouldResetValue tests/BenchmarkDotNet.Tests/Disassemblers/Arm64/Arm64RegisterValueAccumulatorTests.MovzThenUnConditionalBranch.cs:63
- Skipped (documented): MovzThenDrps_ShouldResetValue tests/BenchmarkDotNet.Tests/Disassemblers/Arm64/Arm64RegisterValueAccumulatorTests.MovzThenUnConditionalBranch.cs:84
- Skipped (documented): BelongToGroup_Call tests/BenchmarkDotNet.Tests/Disassemblers/Arm64/BelongsToGroupTests.cs:38
- doc comments repeat the names src/BenchmarkDotNet/Analysers/OutliersAnalyser.cs:39
- doc comments repeat the names src/BenchmarkDotNet.Annotations/Jobs/RuntimeMoniker.cs:31
- doc comments repeat the names src/BenchmarkDotNet.Exporters.Plotting/ScottPlotExporter.cs:26
- doc comments repeat the names tests/BenchmarkDotNet.IntegrationTests/PowerRequestsParser.cs:147
- doc comments repeat the names src/BenchmarkDotNet.TestAdapter/BenchmarkCaseExtensions.cs:73
- doc comments repeat the names src/BenchmarkDotNet.Weaver/src/WeaveAssemblyTask.cs:30
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a10034221aa24369bb2f0e1f5b7d1d4f/history.json --exit-code 0 --source . | 12 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a10034221aa24369bb2f0e1f5b7d1d4f/tree.json --exit-code 0 --source . | 11 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude tests/BenchmarkDotNet.IntegrationTests/InProcess.EmitTests.T4 . | 82 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list BenchmarkDotNet.slnx package --vulnerable --include-transitive --format json | 0 | artifacts/raw/dotnet-vulnerable.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 79 file(s) — `src/BenchmarkDotNet.Annotations/Attributes/AsyncCallerTypeAttribute.cs`, `src/BenchmarkDotNet.Annotations/Attributes/GenericTypeArgumentsAttribute.cs`, `src/BenchmarkDotNet.CodeFixers/ArgumentsSourceElementTypeCodeFixProvider.cs`, `src/BenchmarkDotNet.Diagnostics.dotMemory/DotMemoryDiagnoser.cs`, `src/BenchmarkDotNet.Diagnostics.dotTrace/DotTraceDiagnoser.cs`, … (+74 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 Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |