Executive summary
RicoSuter/NSwag falls short of our standard for production, in part because it has pipeline tools referenced by a changeable name. It scores 48 out of 100 and is rated Weak, and 31 of its 75 critical findings are security problems.
Security and Compliance, at 38, 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 7 points. Restoring certificate checks comes next, worth about 6 points. Raising Security and Compliance to 70 would lift the score to about 56.
Twenty-three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three secrets can leak from the build pipeline, and two pipeline steps run downloads nobody checks. Pinning each tool to an exact version, limiting each secret to its own step and checking each download against a checksum would close these risks. Switching the validation back on would fix the security check on connections or logins switched off, and the password or key in the code and the password or key in the code's history need replacing, with the old ones switched off. The 33 sets of compiler warnings switched off in projects need turning back on in the build file.
The product code is 22,496 lines, about €55,000 to rebuild.
If Security and Compliance rose from 38 to 70, the lowest score rated Strong, the score would rise from 48 to about 56.
New since the last survey: 25 findings
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/NSwag.Sample.NET100/Startup.cs
- Code Duplication · Edited copy of a member (24 corresponding lines) src/NSwag.AspNet.WebApi/JsonExceptionFilterAttribute.cs
- Code Duplication · Edited copy of a member (21 corresponding lines) src/NSwag.AspNet.WebApi/JsonExceptionFilterAttribute.cs
- Code Duplication · Edited copy of a member (19 corresponding lines) src/NSwag.AspNet.Owin/SwaggerExtensions.cs
- Code Duplication · Edited copy of a member (4 corresponding lines) src/NSwag.Core.Yaml/OpenApiYamlDocument.cs
- Code Duplication · Duplicated block (37 lines × 3) REDACTED
- Explicit Debt · BarePragmaDisable REDACTED
- Explicit Debt · NoWarnInCsproj src/NSwag.Sample.NET110Minimal/NSwag.Sample.NET110Minimal.csproj
- Explicit Debt · NoWarnInCsproj src/NSwag.Sample.NET110Minimal/NSwag.Sample.NET110Minimal.csproj
- 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
- Supply-chain Provenance & Signing · REDACTED
- Exception handling · Swallowed exception (empty catch) src/NSwag.Commands/Commands/Generation/AspNetCore/ProjectMetadata.cs
Fixed since the last survey: 22 findings
- Code Coverage · Coverage not measured — no coverage collector is wired up
- Dependency Vulnerabilities · High CVE: Microsoft.OpenApi 2.0.0
- Supply-chain Provenance & Signing · Workflow token permissions not restricted REDACTED
- Supply-chain Provenance & Signing · Workflow token permissions not restricted REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net9.0 src/NSwag.Sample.NET90Minimal/NSwag.Sample.NET90Minimal.csproj
- Cancellation propagation · Async method without CancellationToken: LoadApplicationSettingsAsync src/NSwagStudio/ViewModels/MainWindowModel.cs
- Cancellation propagation · Async method without CancellationToken: OpenDocumentAsync src/NSwagStudio/ViewModels/MainWindowModel.cs
- Cancellation propagation · Async method without CancellationToken: OpenDocumentAsync src/NSwagStudio/ViewModels/MainWindowModel.cs
- Cancellation propagation · Async method without CancellationToken: CloseAllDocumentsAsync src/NSwagStudio/ViewModels/MainWindowModel.cs
- Cancellation propagation · Async method without CancellationToken: CloseDocumentAsync src/NSwagStudio/ViewModels/MainWindowModel.cs
- Cancellation propagation · Async method without CancellationToken: SaveDocumentAsync src/NSwagStudio/ViewModels/MainWindowModel.cs
- Cancellation propagation · Async method without CancellationToken: SaveAllDocumentAsync src/NSwagStudio/ViewModels/MainWindowModel.cs
- Cancellation propagation · Async method without CancellationToken: SaveAsDocumentAsync src/NSwagStudio/ViewModels/MainWindowModel.cs
- Cancellation propagation · Async method without CancellationToken: RunAsync src/NSwag.Commands/Commands/Document/CreateDocumentCommand.cs
- Cancellation propagation · Async method without CancellationToken: CreateDocumentAsync src/NSwag.Commands/Commands/Document/CreateDocumentCommand.cs
- Cancellation propagation · Async method without CancellationToken: ReadUsingMsBuildTargets src/NSwag.Commands/Commands/Generation/AspNetCore/ProjectMetadata.cs
- Cancellation propagation · Async method without CancellationToken: GenerateAsync src/NSwag.AspNetCore/OpenApiDocumentProvider.cs
- Cancellation propagation · Async method without CancellationToken: GenerateAsync src/NSwag.Generation.AspNetCore/AspNetCoreOpenApiDocumentGenerator.cs
- Cancellation propagation · Async method without CancellationToken: CreateDocumentAsync src/NSwag.Generation.AspNetCore/AspNetCoreOpenApiDocumentGenerator.cs
- Cancellation propagation · Async method drops its ambient CancellationToken: Invoke src/NSwag.AspNet.Owin/Middlewares/SwaggerUiIndexMiddleware.cs
- Cancellation propagation · Async method drops its ambient CancellationToken: Invoke src/NSwag.AspNetCore/Middlewares/OpenApiDocumentMiddleware.cs
- A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €55,000 · Estimate
| Cost to rebuild | €18,000 to €92,000, for 300 to 964 hours of work, about 0.4 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 48. 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: 22,496 lines of product code |
| Comment lines | The estimate prices 18,114 lines. Comment lines count towards the size of 22,496 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 Microsoft.Extensions.ApiDescriptions | 2 NConsole | 3 NSwag.Collections | 4 NSwag.Generation.WebApi.Infrastructure | 5 NSwag | 6 NSwag.Commands.Document | 7 NSwag.Commands.Tooling | 8 NSwag.CodeGeneration.OperationNameGenerators | 9 NSwag.Commands.Generation | 10 NSwag.Commands.Generation.AspNetCore | 11 NSwag.Generation.Processors.Contexts | 12 NSwag.CodeGeneration | 13 NSwag.Generation.Processors | 14 NSwag.CodeGeneration.Models | 15 NSwag.Generation.Processors.Collections | 16 NSwag.Generation.Processors.Security | 17 NSwag.CodeGeneration.CSharp.Models | 18 NSwag.CodeGeneration.TypeScript.Models | 19 NSwag.Generation | 20 NSwag.CodeGeneration.CSharp | 21 NSwag.CodeGeneration.TypeScript | 22 NSwag.Generation.AspNetCore | 23 NSwag.Generation.WebApi | 24 Microsoft.Extensions.DependencyInjection | 25 NSwag.AspNet.Owin | 26 NSwag.AspNetCore | 27 NSwag.Commands.CodeGeneration | 28 NSwag.Generation.AspNetCore.Processors | 29 NSwag.Generation.WebApi.Processors | 30 Microsoft.AspNetCore.Builder | 31 NSwag.AspNet.Owin.Middlewares | 32 NSwag.AspNetCore.Middlewares | 33 NSwag.Commands | 34 NSwagStudio | 35 NSwagStudio.ViewModels.CodeGenerators | 36 NSwagStudio.Views.CodeGenerators | 37 NSwagStudio.ViewModels | 38 NSwagStudio.ViewModels.SwaggerGenerators | 39 NSwagStudio.Views | 40 NSwagStudio.Views.SwaggerGenerators |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Microsoft.Extensions.ApiDescriptions | ||||||||||||||||||||||||||||||||||||||||
| 2 NConsole | ||||||||||||||||||||||||||||||||||||||||
| 3 NSwag.Collections | ||||||||||||||||||||||||||||||||||||||||
| 4 NSwag.Generation.WebApi.Infrastructure | ||||||||||||||||||||||||||||||||||||||||
| 5 NSwag | 1 | 5 | ||||||||||||||||||||||||||||||||||||||
| 6 NSwag.Commands.Document | 6 | |||||||||||||||||||||||||||||||||||||||
| 7 NSwag.Commands.Tooling | 3 | |||||||||||||||||||||||||||||||||||||||
| 8 NSwag.CodeGeneration.OperationNameGenerators | 16 | |||||||||||||||||||||||||||||||||||||||
| 9 NSwag.Commands.Generation | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 10 NSwag.Commands.Generation.AspNetCore | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 11 NSwag.Generation.Processors.Contexts | 4 | 3 | ||||||||||||||||||||||||||||||||||||||
| 12 NSwag.CodeGeneration | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 NSwag.Generation.Processors | 4 | 11 | 1 | |||||||||||||||||||||||||||||||||||||
| 14 NSwag.CodeGeneration.Models | 9 | 4 | ||||||||||||||||||||||||||||||||||||||
| 15 NSwag.Generation.Processors.Collections | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 NSwag.Generation.Processors.Security | 2 | 3 | 3 | |||||||||||||||||||||||||||||||||||||
| 17 NSwag.CodeGeneration.CSharp.Models | 11 | 5 | 4 | 10 | ||||||||||||||||||||||||||||||||||||
| 18 NSwag.CodeGeneration.TypeScript.Models | 8 | 3 | 4 | 9 | ||||||||||||||||||||||||||||||||||||
| 19 NSwag.Generation | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 20 NSwag.CodeGeneration.CSharp | 6 | 5 | 5 | |||||||||||||||||||||||||||||||||||||
| 21 NSwag.CodeGeneration.TypeScript | 2 | 4 | 2 | |||||||||||||||||||||||||||||||||||||
| 22 NSwag.Generation.AspNetCore | 6 | 1 | 4 | |||||||||||||||||||||||||||||||||||||
| 23 NSwag.Generation.WebApi | 2 | 3 | 2 | |||||||||||||||||||||||||||||||||||||
| 24 Microsoft.Extensions.DependencyInjection | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 NSwag.AspNet.Owin | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 NSwag.AspNetCore | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 27 NSwag.Commands.CodeGeneration | 12 | 1 | 3 | 1 | 4 | 4 | ||||||||||||||||||||||||||||||||||
| 28 NSwag.Generation.AspNetCore.Processors | 2 | 3 | 4 | 2 | ||||||||||||||||||||||||||||||||||||
| 29 NSwag.Generation.WebApi.Processors | 2 | 3 | 4 | 2 | ||||||||||||||||||||||||||||||||||||
| 30 Microsoft.AspNetCore.Builder | 6 | |||||||||||||||||||||||||||||||||||||||
| 31 NSwag.AspNet.Owin.Middlewares | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 32 NSwag.AspNetCore.Middlewares | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 33 NSwag.Commands | 5 | 4 | 1 | 1 | 1 | 5 | ||||||||||||||||||||||||||||||||||
| 34 NSwagStudio | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 NSwagStudio.ViewModels.CodeGenerators | 1 | 3 | 4 | 6 | 3 | 4 | ||||||||||||||||||||||||||||||||||
| 36 NSwagStudio.Views.CodeGenerators | 8 | 4 | ||||||||||||||||||||||||||||||||||||||
| 37 NSwagStudio.ViewModels | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 NSwagStudio.ViewModels.SwaggerGenerators | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 39 NSwagStudio.Views | 3 | |||||||||||||||||||||||||||||||||||||||
| 40 NSwagStudio.Views.SwaggerGenerators | 1 | 1 | 1 | 5 | 3 | 2 |
5→2 NSwag uses NConsole✕
- Connections
- 1 pair of types, where a type in NSwag uses a type in NConsole.
- The types involved
NSwag.CoreConsoleHost→NConsole.IConsoleHost
- Direction
- NSwag uses NConsole, so a change to NConsole can break NSwag, while a change to NSwag can't break NConsole.
- Position
- Below the diagonal: NSwag uses a module listed above it, which is the healthy direction.
5→3 NSwag uses NSwag.Collections✕
- Connections
- 5 pairs of types, where a type in NSwag uses a type in NSwag.Collections.
- The types involved
NSwag.OpenApiDocument→NSwag.Collections.ObservableDictionaryNSwag.OpenApiHeaders→NSwag.Collections.ObservableDictionaryNSwag.OpenApiOperation→NSwag.Collections.ObservableDictionaryNSwag.OpenApiPathItem→NSwag.Collections.ObservableDictionaryNSwag.OpenApiRequestBody→NSwag.Collections.ObservableDictionary
- Direction
- NSwag uses NSwag.Collections, so a change to NSwag.Collections can break NSwag, while a change to NSwag can't break NSwag.Collections.
- Position
- Below the diagonal: NSwag uses a module listed above it, which is the healthy direction.
6→2 NSwag.Commands.Document uses NConsole✕
- Connections
- 6 pairs of types, where a type in NSwag.Commands.Document uses a type in NConsole.
- The types involved
NSwag.Commands.Document.CreateDocumentCommand→NConsole.CommandLineProcessorNSwag.Commands.Document.CreateDocumentCommand→NConsole.IConsoleCommandNSwag.Commands.Document.CreateDocumentCommand→NConsole.IConsoleHostNSwag.Commands.Document.ExecuteDocumentCommand→NConsole.CommandLineProcessorNSwag.Commands.Document.ExecuteDocumentCommand→NConsole.IConsoleCommandNSwag.Commands.Document.ExecuteDocumentCommand→NConsole.IConsoleHost
- Direction
- NSwag.Commands.Document uses NConsole, so a change to NConsole can break NSwag.Commands.Document, while a change to NSwag.Commands.Document can't break NConsole.
- Position
- Below the diagonal: NSwag.Commands.Document uses a module listed above it, which is the healthy direction.
7→2 NSwag.Commands.Tooling uses NConsole✕
- Connections
- 3 pairs of types, where a type in NSwag.Commands.Tooling uses a type in NConsole.
- The types involved
NSwag.Commands.Tooling.VersionCommand→NConsole.CommandLineProcessorNSwag.Commands.Tooling.VersionCommand→NConsole.IConsoleCommandNSwag.Commands.Tooling.VersionCommand→NConsole.IConsoleHost
- Direction
- NSwag.Commands.Tooling uses NConsole, so a change to NConsole can break NSwag.Commands.Tooling, while a change to NSwag.Commands.Tooling can't break NConsole.
- Position
- Below the diagonal: NSwag.Commands.Tooling uses a module listed above it, which is the healthy direction.
8→5 NSwag.CodeGeneration.OperationNameGenerators uses NSwag✕
- Connections
- 16 pairs of types, where a type in NSwag.CodeGeneration.OperationNameGenerators uses a type in NSwag.
- The types involved
NSwag.CodeGeneration.OperationNameGenerators.IOperationNameGenerator→NSwag.OpenApiDocumentNSwag.CodeGeneration.OperationNameGenerators.IOperationNameGenerator→NSwag.OpenApiOperationNSwag.CodeGeneration.OperationNameGenerators.MultipleClientsFromFirstTagAndOperationIdGenerator→NSwag.OpenApiDocumentNSwag.CodeGeneration.OperationNameGenerators.MultipleClientsFromFirstTagAndOperationIdGenerator→NSwag.OpenApiOperationNSwag.CodeGeneration.OperationNameGenerators.MultipleClientsFromFirstTagAndOperationNameGenerator→NSwag.OpenApiDocumentNSwag.CodeGeneration.OperationNameGenerators.MultipleClientsFromFirstTagAndOperationNameGenerator→NSwag.OpenApiOperationNSwag.CodeGeneration.OperationNameGenerators.MultipleClientsFromFirstTagAndPathSegmentsOperationNameGenerator→NSwag.OpenApiDocumentNSwag.CodeGeneration.OperationNameGenerators.MultipleClientsFromFirstTagAndPathSegmentsOperationNameGenerator→NSwag.OpenApiOperationNSwag.CodeGeneration.OperationNameGenerators.MultipleClientsFromOperationIdOperationNameGenerator→NSwag.OpenApiDocumentNSwag.CodeGeneration.OperationNameGenerators.MultipleClientsFromOperationIdOperationNameGenerator→NSwag.OpenApiOperationNSwag.CodeGeneration.OperationNameGenerators.MultipleClientsFromPathSegmentsOperationNameGenerator→NSwag.OpenApiDocumentNSwag.CodeGeneration.OperationNameGenerators.MultipleClientsFromPathSegmentsOperationNameGenerator→NSwag.OpenApiOperationNSwag.CodeGeneration.OperationNameGenerators.SingleClientFromOperationIdOperationNameGenerator→NSwag.OpenApiDocumentNSwag.CodeGeneration.OperationNameGenerators.SingleClientFromOperationIdOperationNameGenerator→NSwag.OpenApiOperationNSwag.CodeGeneration.OperationNameGenerators.SingleClientFromPathSegmentsOperationNameGenerator→NSwag.OpenApiDocumentNSwag.CodeGeneration.OperationNameGenerators.SingleClientFromPathSegmentsOperationNameGenerator→NSwag.OpenApiOperation
- Direction
- NSwag.CodeGeneration.OperationNameGenerators uses NSwag, so a change to NSwag can break NSwag.CodeGeneration.OperationNameGenerators, while a change to NSwag.CodeGeneration.OperationNameGenerators can't break NSwag.
- Position
- Below the diagonal: NSwag.CodeGeneration.OperationNameGenerators uses a module listed above it, which is the healthy direction.
9→2 NSwag.Commands.Generation uses NConsole✕
- Connections
- 2 pairs of types, where a type in NSwag.Commands.Generation uses a type in NConsole.
- The types involved
NSwag.Commands.Generation.FromDocumentCommand→NConsole.CommandLineProcessorNSwag.Commands.Generation.FromDocumentCommand→NConsole.IConsoleHost
- Direction
- NSwag.Commands.Generation uses NConsole, so a change to NConsole can break NSwag.Commands.Generation, while a change to NSwag.Commands.Generation can't break NConsole.
- Position
- Below the diagonal: NSwag.Commands.Generation uses a module listed above it, which is the healthy direction.
9→5 NSwag.Commands.Generation uses NSwag✕
- Connections
- 1 pair of types, where a type in NSwag.Commands.Generation uses a type in NSwag.
- The types involved
NSwag.Commands.Generation.FromDocumentCommand→NSwag.OpenApiDocument
- Direction
- NSwag.Commands.Generation uses NSwag, so a change to NSwag can break NSwag.Commands.Generation, while a change to NSwag.Commands.Generation can't break NSwag.
- Position
- Below the diagonal: NSwag.Commands.Generation uses a module listed above it, which is the healthy direction.
9→33 NSwag.Commands.Generation uses NSwag.Commands part of a loop✕
- Connections
- 1 pair of types, where a type in NSwag.Commands.Generation uses a type in NSwag.Commands.
- The types involved
NSwag.Commands.Generation.FromDocumentCommand→NSwag.Commands.OutputCommandBase
- Direction
- NSwag.Commands.Generation uses NSwag.Commands, so a change to NSwag.Commands can break NSwag.Commands.Generation, while a change to NSwag.Commands.Generation can't break NSwag.Commands.
- 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 NSwag.Commands.Generation.AspNetCore uses NConsole✕
- Connections
- 4 pairs of types, where a type in NSwag.Commands.Generation.AspNetCore uses a type in NConsole.
- The types involved
NSwag.Commands.Generation.AspNetCore.AspNetCoreToOpenApiCommand→NConsole.CommandLineProcessorNSwag.Commands.Generation.AspNetCore.AspNetCoreToOpenApiCommand→NConsole.IConsoleHostNSwag.Commands.Generation.AspNetCore.Exe→NConsole.IConsoleHostNSwag.Commands.Generation.AspNetCore.ProjectMetadata→NConsole.IConsoleHost
- Direction
- NSwag.Commands.Generation.AspNetCore uses NConsole, so a change to NConsole can break NSwag.Commands.Generation.AspNetCore, while a change to NSwag.Commands.Generation.AspNetCore can't break NConsole.
- Position
- Below the diagonal: NSwag.Commands.Generation.AspNetCore uses a module listed above it, which is the healthy direction.
10→5 NSwag.Commands.Generation.AspNetCore uses NSwag✕
- Connections
- 1 pair of types, where a type in NSwag.Commands.Generation.AspNetCore uses a type in NSwag.
- The types involved
NSwag.Commands.Generation.AspNetCore.AspNetCoreToOpenApiCommand→NSwag.OpenApiDocument
- Direction
- NSwag.Commands.Generation.AspNetCore uses NSwag, so a change to NSwag can break NSwag.Commands.Generation.AspNetCore, while a change to NSwag.Commands.Generation.AspNetCore can't break NSwag.
- Position
- Below the diagonal: NSwag.Commands.Generation.AspNetCore uses a module listed above it, which is the healthy direction.
10→33 NSwag.Commands.Generation.AspNetCore uses NSwag.Commands part of a loop✕
- Connections
- 1 pair of types, where a type in NSwag.Commands.Generation.AspNetCore uses a type in NSwag.Commands.
- The types involved
NSwag.Commands.Generation.AspNetCore.AspNetCoreToOpenApiCommand→NSwag.Commands.OutputCommandBase
- Direction
- NSwag.Commands.Generation.AspNetCore uses NSwag.Commands, so a change to NSwag.Commands can break NSwag.Commands.Generation.AspNetCore, while a change to NSwag.Commands.Generation.AspNetCore can't break NSwag.Commands.
- 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→5 NSwag.Generation.Processors.Contexts uses NSwag✕
- Connections
- 4 pairs of types, where a type in NSwag.Generation.Processors.Contexts uses a type in NSwag.
- The types involved
NSwag.Generation.Processors.Contexts.DocumentProcessorContext→NSwag.OpenApiDocumentNSwag.Generation.Processors.Contexts.OperationProcessorContext→NSwag.OpenApiDocumentNSwag.Generation.Processors.Contexts.OperationProcessorContext→NSwag.OpenApiOperationDescriptionNSwag.Generation.Processors.Contexts.OperationProcessorContext→NSwag.OpenApiParameter
- Direction
- NSwag.Generation.Processors.Contexts uses NSwag, so a change to NSwag can break NSwag.Generation.Processors.Contexts, while a change to NSwag.Generation.Processors.Contexts can't break NSwag.
- Position
- Below the diagonal: NSwag.Generation.Processors.Contexts uses a module listed above it, which is the healthy direction.
11→19 NSwag.Generation.Processors.Contexts uses NSwag.Generation part of a loop✕
- Connections
- 3 pairs of types, where a type in NSwag.Generation.Processors.Contexts uses a type in NSwag.Generation.
- The types involved
NSwag.Generation.Processors.Contexts.DocumentProcessorContext→NSwag.Generation.OpenApiDocumentGeneratorSettingsNSwag.Generation.Processors.Contexts.OperationProcessorContext→NSwag.Generation.OpenApiDocumentGeneratorNSwag.Generation.Processors.Contexts.OperationProcessorContext→NSwag.Generation.OpenApiDocumentGeneratorSettings
- Direction
- NSwag.Generation.Processors.Contexts uses NSwag.Generation, so a change to NSwag.Generation can break NSwag.Generation.Processors.Contexts, while a change to NSwag.Generation.Processors.Contexts can't break NSwag.Generation.
- 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→5 NSwag.CodeGeneration uses NSwag✕
- Connections
- 4 pairs of types, where a type in NSwag.CodeGeneration uses a type in NSwag.
- The types involved
NSwag.CodeGeneration.ClientGeneratorBase→NSwag.OpenApiDocumentNSwag.CodeGeneration.ClientGeneratorBase→NSwag.OpenApiOperationNSwag.CodeGeneration.DefaultParameterNameGenerator→NSwag.OpenApiParameterNSwag.CodeGeneration.IParameterNameGenerator→NSwag.OpenApiParameter
- Direction
- NSwag.CodeGeneration uses NSwag, so a change to NSwag can break NSwag.CodeGeneration, while a change to NSwag.CodeGeneration can't break NSwag.
- Position
- Below the diagonal: NSwag.CodeGeneration uses a module listed above it, which is the healthy direction.
12→8 NSwag.CodeGeneration uses NSwag.CodeGeneration.OperationNameGenerators✕
- Connections
- 1 pair of types, where a type in NSwag.CodeGeneration uses a type in NSwag.CodeGeneration.OperationNameGenerators.
- The types involved
NSwag.CodeGeneration.ClientGeneratorBaseSettings→NSwag.CodeGeneration.OperationNameGenerators.IOperationNameGenerator
- Direction
- NSwag.CodeGeneration uses NSwag.CodeGeneration.OperationNameGenerators, so a change to NSwag.CodeGeneration.OperationNameGenerators can break NSwag.CodeGeneration, while a change to NSwag.CodeGeneration can't break NSwag.CodeGeneration.OperationNameGenerators.
- Position
- Below the diagonal: NSwag.CodeGeneration uses a module listed above it, which is the healthy direction.
13→5 NSwag.Generation.Processors uses NSwag✕
- Connections
- 4 pairs of types, where a type in NSwag.Generation.Processors uses a type in NSwag.
- The types involved
NSwag.Generation.Processors.DocumentTagsProcessor→NSwag.OpenApiDocumentNSwag.Generation.Processors.OperationResponseProcessorBase→NSwag.JsonExpectedSchemaNSwag.Generation.Processors.OperationTagsProcessor→NSwag.OpenApiDocumentNSwag.Generation.Processors.OperationTagsProcessor→NSwag.OpenApiOperationDescription
- Direction
- NSwag.Generation.Processors uses NSwag, so a change to NSwag can break NSwag.Generation.Processors, while a change to NSwag.Generation.Processors can't break NSwag.
- Position
- Below the diagonal: NSwag.Generation.Processors uses a module listed above it, which is the healthy direction.
13→11 NSwag.Generation.Processors uses NSwag.Generation.Processors.Contexts✕
- Connections
- 11 pairs of types, where a type in NSwag.Generation.Processors uses a type in NSwag.Generation.Processors.Contexts.
- The types involved
NSwag.Generation.Processors.ActionDocumentProcessor→NSwag.Generation.Processors.Contexts.DocumentProcessorContextNSwag.Generation.Processors.ApiVersionProcessor→NSwag.Generation.Processors.Contexts.OperationProcessorContextNSwag.Generation.Processors.DocumentExtensionDataProcessor→NSwag.Generation.Processors.Contexts.DocumentProcessorContextNSwag.Generation.Processors.DocumentTagsProcessor→NSwag.Generation.Processors.Contexts.DocumentProcessorContextNSwag.Generation.Processors.IDocumentProcessor→NSwag.Generation.Processors.Contexts.DocumentProcessorContextNSwag.Generation.Processors.IOperationProcessor→NSwag.Generation.Processors.Contexts.OperationProcessorContextNSwag.Generation.Processors.OperationExtensionDataProcessor→NSwag.Generation.Processors.Contexts.OperationProcessorContextNSwag.Generation.Processors.OperationProcessor→NSwag.Generation.Processors.Contexts.OperationProcessorContextNSwag.Generation.Processors.OperationResponseProcessorBase→NSwag.Generation.Processors.Contexts.OperationProcessorContextNSwag.Generation.Processors.OperationSummaryAndDescriptionProcessor→NSwag.Generation.Processors.Contexts.OperationProcessorContextNSwag.Generation.Processors.OperationTagsProcessor→NSwag.Generation.Processors.Contexts.OperationProcessorContext
- Direction
- NSwag.Generation.Processors uses NSwag.Generation.Processors.Contexts, so a change to NSwag.Generation.Processors.Contexts can break NSwag.Generation.Processors, while a change to NSwag.Generation.Processors can't break NSwag.Generation.Processors.Contexts.
- Position
- Below the diagonal: NSwag.Generation.Processors uses a module listed above it, which is the healthy direction.
13→19 NSwag.Generation.Processors uses NSwag.Generation part of a loop✕
- Connections
- 1 pair of types, where a type in NSwag.Generation.Processors uses a type in NSwag.Generation.
- The types involved
NSwag.Generation.Processors.OperationResponseProcessorBase→NSwag.Generation.OpenApiDocumentGeneratorSettings
- Direction
- NSwag.Generation.Processors uses NSwag.Generation, so a change to NSwag.Generation can break NSwag.Generation.Processors, while a change to NSwag.Generation.Processors can't break NSwag.Generation.
- 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→5 NSwag.CodeGeneration.Models uses NSwag✕
- Connections
- 9 pairs of types, where a type in NSwag.CodeGeneration.Models uses a type in NSwag.
- The types involved
NSwag.CodeGeneration.Models.OperationModelBase→NSwag.OpenApiOperationNSwag.CodeGeneration.Models.OperationModelBase→NSwag.OpenApiParameterNSwag.CodeGeneration.Models.OperationModelBase→NSwag.OpenApiResponseNSwag.CodeGeneration.Models.ParameterModelBase→NSwag.OpenApiParameterNSwag.CodeGeneration.Models.ParameterModelBase→NSwag.OpenApiParameterKindNSwag.CodeGeneration.Models.ParameterModelBase→NSwag.OpenApiParameterStyleNSwag.CodeGeneration.Models.ResponseModelBase→NSwag.JsonExpectedSchemaNSwag.CodeGeneration.Models.ResponseModelBase→NSwag.OpenApiOperationNSwag.CodeGeneration.Models.ResponseModelBase→NSwag.OpenApiResponse
- Direction
- NSwag.CodeGeneration.Models uses NSwag, so a change to NSwag can break NSwag.CodeGeneration.Models, while a change to NSwag.CodeGeneration.Models can't break NSwag.
- Position
- Below the diagonal: NSwag.CodeGeneration.Models uses a module listed above it, which is the healthy direction.
14→12 NSwag.CodeGeneration.Models uses NSwag.CodeGeneration✕
- Connections
- 4 pairs of types, where a type in NSwag.CodeGeneration.Models uses a type in NSwag.CodeGeneration.
- The types involved
NSwag.CodeGeneration.Models.OperationModelBase→NSwag.CodeGeneration.ClientGeneratorBaseSettingsNSwag.CodeGeneration.Models.OperationModelBase→NSwag.CodeGeneration.IClientGeneratorNSwag.CodeGeneration.Models.ParameterModelBase→NSwag.CodeGeneration.IClientGeneratorNSwag.CodeGeneration.Models.ResponseModelBase→NSwag.CodeGeneration.IClientGenerator
- Direction
- NSwag.CodeGeneration.Models uses NSwag.CodeGeneration, so a change to NSwag.CodeGeneration can break NSwag.CodeGeneration.Models, while a change to NSwag.CodeGeneration.Models can't break NSwag.CodeGeneration.
- Position
- Below the diagonal: NSwag.CodeGeneration.Models uses a module listed above it, which is the healthy direction.
15→13 NSwag.Generation.Processors.Collections uses NSwag.Generation.Processors✕
- Connections
- 1 pair of types, where a type in NSwag.Generation.Processors.Collections uses a type in NSwag.Generation.Processors.
- The types involved
NSwag.Generation.Processors.Collections.OperationProcessorCollection→NSwag.Generation.Processors.IOperationProcessor
- Direction
- NSwag.Generation.Processors.Collections uses NSwag.Generation.Processors, so a change to NSwag.Generation.Processors can break NSwag.Generation.Processors.Collections, while a change to NSwag.Generation.Processors.Collections can't break NSwag.Generation.Processors.
- Position
- Below the diagonal: NSwag.Generation.Processors.Collections uses a module listed above it, which is the healthy direction.
16→5 NSwag.Generation.Processors.Security uses NSwag✕
- Connections
- 2 pairs of types, where a type in NSwag.Generation.Processors.Security uses a type in NSwag.
- The types involved
NSwag.Generation.Processors.Security.OperationSecurityScopeProcessor→NSwag.OpenApiOperationDescriptionNSwag.Generation.Processors.Security.SecurityDefinitionAppender→NSwag.OpenApiSecurityScheme
- Direction
- NSwag.Generation.Processors.Security uses NSwag, so a change to NSwag can break NSwag.Generation.Processors.Security, while a change to NSwag.Generation.Processors.Security can't break NSwag.
- Position
- Below the diagonal: NSwag.Generation.Processors.Security uses a module listed above it, which is the healthy direction.
16→11 NSwag.Generation.Processors.Security uses NSwag.Generation.Processors.Contexts✕
- Connections
- 3 pairs of types, where a type in NSwag.Generation.Processors.Security uses a type in NSwag.Generation.Processors.Contexts.
- The types involved
NSwag.Generation.Processors.Security.AspNetCoreOperationSecurityScopeProcessor→NSwag.Generation.Processors.Contexts.OperationProcessorContextNSwag.Generation.Processors.Security.OperationSecurityScopeProcessor→NSwag.Generation.Processors.Contexts.OperationProcessorContextNSwag.Generation.Processors.Security.SecurityDefinitionAppender→NSwag.Generation.Processors.Contexts.DocumentProcessorContext
- Direction
- NSwag.Generation.Processors.Security uses NSwag.Generation.Processors.Contexts, so a change to NSwag.Generation.Processors.Contexts can break NSwag.Generation.Processors.Security, while a change to NSwag.Generation.Processors.Security can't break NSwag.Generation.Processors.Contexts.
- Position
- Below the diagonal: NSwag.Generation.Processors.Security uses a module listed above it, which is the healthy direction.
16→13 NSwag.Generation.Processors.Security uses NSwag.Generation.Processors✕
- Connections
- 3 pairs of types, where a type in NSwag.Generation.Processors.Security uses a type in NSwag.Generation.Processors.
- The types involved
NSwag.Generation.Processors.Security.AspNetCoreOperationSecurityScopeProcessor→NSwag.Generation.Processors.IOperationProcessorNSwag.Generation.Processors.Security.OperationSecurityScopeProcessor→NSwag.Generation.Processors.IOperationProcessorNSwag.Generation.Processors.Security.SecurityDefinitionAppender→NSwag.Generation.Processors.IDocumentProcessor
- Direction
- NSwag.Generation.Processors.Security uses NSwag.Generation.Processors, so a change to NSwag.Generation.Processors can break NSwag.Generation.Processors.Security, while a change to NSwag.Generation.Processors.Security can't break NSwag.Generation.Processors.
- Position
- Below the diagonal: NSwag.Generation.Processors.Security uses a module listed above it, which is the healthy direction.
17→5 NSwag.CodeGeneration.CSharp.Models uses NSwag✕
- Connections
- 11 pairs of types, where a type in NSwag.CodeGeneration.CSharp.Models uses a type in NSwag.
- The types involved
NSwag.CodeGeneration.CSharp.Models.CSharpClientTemplateModel→NSwag.OpenApiDocumentNSwag.CodeGeneration.CSharp.Models.CSharpControllerOperationModel→NSwag.OpenApiOperationNSwag.CodeGeneration.CSharp.Models.CSharpControllerTemplateModel→NSwag.OpenApiDocumentNSwag.CodeGeneration.CSharp.Models.CSharpFileTemplateModel→NSwag.OpenApiDocumentNSwag.CodeGeneration.CSharp.Models.CSharpOperationModel→NSwag.OpenApiOperationNSwag.CodeGeneration.CSharp.Models.CSharpOperationModel→NSwag.OpenApiParameterNSwag.CodeGeneration.CSharp.Models.CSharpOperationModel→NSwag.OpenApiResponseNSwag.CodeGeneration.CSharp.Models.CSharpOperationModel→NSwag.OpenApiSecurityRequirementNSwag.CodeGeneration.CSharp.Models.CSharpParameterModel→NSwag.OpenApiParameterNSwag.CodeGeneration.CSharp.Models.CSharpResponseModel→NSwag.OpenApiOperationNSwag.CodeGeneration.CSharp.Models.CSharpResponseModel→NSwag.OpenApiResponse
- Direction
- NSwag.CodeGeneration.CSharp.Models uses NSwag, so a change to NSwag can break NSwag.CodeGeneration.CSharp.Models, while a change to NSwag.CodeGeneration.CSharp.Models can't break NSwag.
- Position
- Below the diagonal: NSwag.CodeGeneration.CSharp.Models uses a module listed above it, which is the healthy direction.
17→12 NSwag.CodeGeneration.CSharp.Models uses NSwag.CodeGeneration✕
- Connections
- 5 pairs of types, where a type in NSwag.CodeGeneration.CSharp.Models uses a type in NSwag.CodeGeneration.
- The types involved
NSwag.CodeGeneration.CSharp.Models.CSharpFileTemplateModel→NSwag.CodeGeneration.ClientGeneratorOutputTypeNSwag.CodeGeneration.CSharp.Models.CSharpOperationModel→NSwag.CodeGeneration.ClientGeneratorBaseSettingsNSwag.CodeGeneration.CSharp.Models.CSharpOperationModel→NSwag.CodeGeneration.IClientGeneratorNSwag.CodeGeneration.CSharp.Models.CSharpParameterModel→NSwag.CodeGeneration.IClientGeneratorNSwag.CodeGeneration.CSharp.Models.CSharpResponseModel→NSwag.CodeGeneration.IClientGenerator
- Direction
- NSwag.CodeGeneration.CSharp.Models uses NSwag.CodeGeneration, so a change to NSwag.CodeGeneration can break NSwag.CodeGeneration.CSharp.Models, while a change to NSwag.CodeGeneration.CSharp.Models can't break NSwag.CodeGeneration.
- Position
- Below the diagonal: NSwag.CodeGeneration.CSharp.Models uses a module listed above it, which is the healthy direction.
17→14 NSwag.CodeGeneration.CSharp.Models uses NSwag.CodeGeneration.Models✕
- Connections
- 4 pairs of types, where a type in NSwag.CodeGeneration.CSharp.Models uses a type in NSwag.CodeGeneration.Models.
- The types involved
NSwag.CodeGeneration.CSharp.Models.CSharpOperationModel→NSwag.CodeGeneration.Models.OperationModelBaseNSwag.CodeGeneration.CSharp.Models.CSharpParameterModel→NSwag.CodeGeneration.Models.ParameterModelBaseNSwag.CodeGeneration.CSharp.Models.CSharpResponseModel→NSwag.CodeGeneration.Models.IOperationModelNSwag.CodeGeneration.CSharp.Models.CSharpResponseModel→NSwag.CodeGeneration.Models.ResponseModelBase
- Direction
- NSwag.CodeGeneration.CSharp.Models uses NSwag.CodeGeneration.Models, so a change to NSwag.CodeGeneration.Models can break NSwag.CodeGeneration.CSharp.Models, while a change to NSwag.CodeGeneration.CSharp.Models can't break NSwag.CodeGeneration.Models.
- Position
- Below the diagonal: NSwag.CodeGeneration.CSharp.Models uses a module listed above it, which is the healthy direction.
17→20 NSwag.CodeGeneration.CSharp.Models uses NSwag.CodeGeneration.CSharp part of a loop✕
- Connections
- 10 pairs of types, where a type in NSwag.CodeGeneration.CSharp.Models uses a type in NSwag.CodeGeneration.CSharp.
- The types involved
NSwag.CodeGeneration.CSharp.Models.CSharpClientTemplateModel→NSwag.CodeGeneration.CSharp.CSharpClientGeneratorSettingsNSwag.CodeGeneration.CSharp.Models.CSharpControllerOperationModel→NSwag.CodeGeneration.CSharp.CSharpControllerGeneratorNSwag.CodeGeneration.CSharp.Models.CSharpControllerOperationModel→NSwag.CodeGeneration.CSharp.CSharpControllerGeneratorSettingsNSwag.CodeGeneration.CSharp.Models.CSharpControllerTemplateModel→NSwag.CodeGeneration.CSharp.CSharpControllerGeneratorSettingsNSwag.CodeGeneration.CSharp.Models.CSharpExceptionDescriptionModel→NSwag.CodeGeneration.CSharp.CSharpClientGeneratorSettingsNSwag.CodeGeneration.CSharp.Models.CSharpFileTemplateModel→NSwag.CodeGeneration.CSharp.CSharpGeneratorBaseNSwag.CodeGeneration.CSharp.Models.CSharpFileTemplateModel→NSwag.CodeGeneration.CSharp.CSharpGeneratorBaseSettingsNSwag.CodeGeneration.CSharp.Models.CSharpOperationModel→NSwag.CodeGeneration.CSharp.CSharpGeneratorBaseNSwag.CodeGeneration.CSharp.Models.CSharpOperationModel→NSwag.CodeGeneration.CSharp.CSharpGeneratorBaseSettingsNSwag.CodeGeneration.CSharp.Models.CSharpTemplateModelBase→NSwag.CodeGeneration.CSharp.CSharpGeneratorBaseSettings
- Direction
- NSwag.CodeGeneration.CSharp.Models uses NSwag.CodeGeneration.CSharp, so a change to NSwag.CodeGeneration.CSharp can break NSwag.CodeGeneration.CSharp.Models, while a change to NSwag.CodeGeneration.CSharp.Models can't break NSwag.CodeGeneration.CSharp.
- 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→5 NSwag.CodeGeneration.TypeScript.Models uses NSwag✕
- Connections
- 8 pairs of types, where a type in NSwag.CodeGeneration.TypeScript.Models uses a type in NSwag.
- The types involved
NSwag.CodeGeneration.TypeScript.Models.TypeScriptClientTemplateModel→NSwag.OpenApiDocumentNSwag.CodeGeneration.TypeScript.Models.TypeScriptFileTemplateModel→NSwag.OpenApiDocumentNSwag.CodeGeneration.TypeScript.Models.TypeScriptOperationModel→NSwag.OpenApiOperationNSwag.CodeGeneration.TypeScript.Models.TypeScriptOperationModel→NSwag.OpenApiParameterNSwag.CodeGeneration.TypeScript.Models.TypeScriptOperationModel→NSwag.OpenApiResponseNSwag.CodeGeneration.TypeScript.Models.TypeScriptParameterModel→NSwag.OpenApiParameterNSwag.CodeGeneration.TypeScript.Models.TypeScriptResponseModel→NSwag.OpenApiOperationNSwag.CodeGeneration.TypeScript.Models.TypeScriptResponseModel→NSwag.OpenApiResponse
- Direction
- NSwag.CodeGeneration.TypeScript.Models uses NSwag, so a change to NSwag can break NSwag.CodeGeneration.TypeScript.Models, while a change to NSwag.CodeGeneration.TypeScript.Models can't break NSwag.
- Position
- Below the diagonal: NSwag.CodeGeneration.TypeScript.Models uses a module listed above it, which is the healthy direction.
18→12 NSwag.CodeGeneration.TypeScript.Models uses NSwag.CodeGeneration✕
- Connections
- 3 pairs of types, where a type in NSwag.CodeGeneration.TypeScript.Models uses a type in NSwag.CodeGeneration.
- The types involved
NSwag.CodeGeneration.TypeScript.Models.TypeScriptOperationModel→NSwag.CodeGeneration.ClientGeneratorBaseSettingsNSwag.CodeGeneration.TypeScript.Models.TypeScriptOperationModel→NSwag.CodeGeneration.IClientGeneratorNSwag.CodeGeneration.TypeScript.Models.TypeScriptResponseModel→NSwag.CodeGeneration.IClientGenerator
- Direction
- NSwag.CodeGeneration.TypeScript.Models uses NSwag.CodeGeneration, so a change to NSwag.CodeGeneration can break NSwag.CodeGeneration.TypeScript.Models, while a change to NSwag.CodeGeneration.TypeScript.Models can't break NSwag.CodeGeneration.
- Position
- Below the diagonal: NSwag.CodeGeneration.TypeScript.Models uses a module listed above it, which is the healthy direction.
18→14 NSwag.CodeGeneration.TypeScript.Models uses NSwag.CodeGeneration.Models✕
- Connections
- 4 pairs of types, where a type in NSwag.CodeGeneration.TypeScript.Models uses a type in NSwag.CodeGeneration.Models.
- The types involved
NSwag.CodeGeneration.TypeScript.Models.TypeScriptOperationModel→NSwag.CodeGeneration.Models.OperationModelBaseNSwag.CodeGeneration.TypeScript.Models.TypeScriptParameterModel→NSwag.CodeGeneration.Models.ParameterModelBaseNSwag.CodeGeneration.TypeScript.Models.TypeScriptResponseModel→NSwag.CodeGeneration.Models.IOperationModelNSwag.CodeGeneration.TypeScript.Models.TypeScriptResponseModel→NSwag.CodeGeneration.Models.ResponseModelBase
- Direction
- NSwag.CodeGeneration.TypeScript.Models uses NSwag.CodeGeneration.Models, so a change to NSwag.CodeGeneration.Models can break NSwag.CodeGeneration.TypeScript.Models, while a change to NSwag.CodeGeneration.TypeScript.Models can't break NSwag.CodeGeneration.Models.
- Position
- Below the diagonal: NSwag.CodeGeneration.TypeScript.Models uses a module listed above it, which is the healthy direction.
18→21 NSwag.CodeGeneration.TypeScript.Models uses NSwag.CodeGeneration.TypeScript part of a loop✕
- Connections
- 9 pairs of types, where a type in NSwag.CodeGeneration.TypeScript.Models uses a type in NSwag.CodeGeneration.TypeScript.
- The types involved
NSwag.CodeGeneration.TypeScript.Models.TypeScriptClientTemplateModel→NSwag.CodeGeneration.TypeScript.TypeScriptClientGeneratorSettingsNSwag.CodeGeneration.TypeScript.Models.TypeScriptFileTemplateModel→NSwag.CodeGeneration.TypeScript.TypeScriptClientGeneratorSettingsNSwag.CodeGeneration.TypeScript.Models.TypeScriptFrameworkAngularModel→NSwag.CodeGeneration.TypeScript.TypeScriptClientGeneratorSettingsNSwag.CodeGeneration.TypeScript.Models.TypeScriptFrameworkModel→NSwag.CodeGeneration.TypeScript.TypeScriptClientGeneratorSettingsNSwag.CodeGeneration.TypeScript.Models.TypeScriptOperationModel→NSwag.CodeGeneration.TypeScript.TypeScriptClientGeneratorNSwag.CodeGeneration.TypeScript.Models.TypeScriptOperationModel→NSwag.CodeGeneration.TypeScript.TypeScriptClientGeneratorSettingsNSwag.CodeGeneration.TypeScript.Models.TypeScriptParameterModel→NSwag.CodeGeneration.TypeScript.TypeScriptClientGeneratorNSwag.CodeGeneration.TypeScript.Models.TypeScriptParameterModel→NSwag.CodeGeneration.TypeScript.TypeScriptClientGeneratorSettingsNSwag.CodeGeneration.TypeScript.Models.TypeScriptResponseModel→NSwag.CodeGeneration.TypeScript.TypeScriptClientGeneratorSettings
- Direction
- NSwag.CodeGeneration.TypeScript.Models uses NSwag.CodeGeneration.TypeScript, so a change to NSwag.CodeGeneration.TypeScript can break NSwag.CodeGeneration.TypeScript.Models, while a change to NSwag.CodeGeneration.TypeScript.Models can't break NSwag.CodeGeneration.TypeScript.
- 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→5 NSwag.Generation uses NSwag✕
- Connections
- 2 pairs of types, where a type in NSwag.Generation uses a type in NSwag.
- The types involved
NSwag.Generation.IOpenApiDocumentGenerator→NSwag.OpenApiDocumentNSwag.Generation.OpenApiDocumentGenerator→NSwag.OpenApiParameter
- Direction
- NSwag.Generation uses NSwag, so a change to NSwag can break NSwag.Generation, while a change to NSwag.Generation can't break NSwag.
- Position
- Below the diagonal: NSwag.Generation uses a module listed above it, which is the healthy direction.
19→11 NSwag.Generation uses NSwag.Generation.Processors.Contexts✕
- Connections
- 1 pair of types, where a type in NSwag.Generation uses a type in NSwag.Generation.Processors.Contexts.
- The types involved
NSwag.Generation.OpenApiDocumentGeneratorSettings→NSwag.Generation.Processors.Contexts.OperationProcessorContext
- Direction
- NSwag.Generation uses NSwag.Generation.Processors.Contexts, so a change to NSwag.Generation.Processors.Contexts can break NSwag.Generation, while a change to NSwag.Generation can't break NSwag.Generation.Processors.Contexts.
- Position
- Below the diagonal: NSwag.Generation uses a module listed above it, which is the healthy direction.
19→15 NSwag.Generation uses NSwag.Generation.Processors.Collections✕
- Connections
- 2 pairs of types, where a type in NSwag.Generation uses a type in NSwag.Generation.Processors.Collections.
- The types involved
NSwag.Generation.OpenApiDocumentGeneratorSettings→NSwag.Generation.Processors.Collections.DocumentProcessorCollectionNSwag.Generation.OpenApiDocumentGeneratorSettings→NSwag.Generation.Processors.Collections.OperationProcessorCollection
- Direction
- NSwag.Generation uses NSwag.Generation.Processors.Collections, so a change to NSwag.Generation.Processors.Collections can break NSwag.Generation, while a change to NSwag.Generation can't break NSwag.Generation.Processors.Collections.
- Position
- Below the diagonal: NSwag.Generation uses a module listed above it, which is the healthy direction.
20→5 NSwag.CodeGeneration.CSharp uses NSwag✕
- Connections
- 6 pairs of types, where a type in NSwag.CodeGeneration.CSharp uses a type in NSwag.
- The types involved
NSwag.CodeGeneration.CSharp.CSharpClientGenerator→NSwag.OpenApiDocumentNSwag.CodeGeneration.CSharp.CSharpClientGenerator→NSwag.OpenApiOperationNSwag.CodeGeneration.CSharp.CSharpControllerGenerator→NSwag.OpenApiDocumentNSwag.CodeGeneration.CSharp.CSharpControllerGenerator→NSwag.OpenApiOperationNSwag.CodeGeneration.CSharp.CSharpControllerGeneratorSettings→NSwag.OpenApiOperationNSwag.CodeGeneration.CSharp.CSharpGeneratorBase→NSwag.OpenApiDocument
- Direction
- NSwag.CodeGeneration.CSharp uses NSwag, so a change to NSwag can break NSwag.CodeGeneration.CSharp, while a change to NSwag.CodeGeneration.CSharp can't break NSwag.
- Position
- Below the diagonal: NSwag.CodeGeneration.CSharp uses a module listed above it, which is the healthy direction.
20→12 NSwag.CodeGeneration.CSharp uses NSwag.CodeGeneration✕
- Connections
- 5 pairs of types, where a type in NSwag.CodeGeneration.CSharp uses a type in NSwag.CodeGeneration.
- The types involved
NSwag.CodeGeneration.CSharp.CSharpClientGenerator→NSwag.CodeGeneration.ClientGeneratorBaseSettingsNSwag.CodeGeneration.CSharp.CSharpControllerGenerator→NSwag.CodeGeneration.ClientGeneratorBaseSettingsNSwag.CodeGeneration.CSharp.CSharpGeneratorBase→NSwag.CodeGeneration.ClientGeneratorBaseNSwag.CodeGeneration.CSharp.CSharpGeneratorBase→NSwag.CodeGeneration.ClientGeneratorOutputTypeNSwag.CodeGeneration.CSharp.CSharpGeneratorBaseSettings→NSwag.CodeGeneration.ClientGeneratorBaseSettings
- Direction
- NSwag.CodeGeneration.CSharp uses NSwag.CodeGeneration, so a change to NSwag.CodeGeneration can break NSwag.CodeGeneration.CSharp, while a change to NSwag.CodeGeneration.CSharp can't break NSwag.CodeGeneration.
- Position
- Below the diagonal: NSwag.CodeGeneration.CSharp uses a module listed above it, which is the healthy direction.
20→17 NSwag.CodeGeneration.CSharp uses NSwag.CodeGeneration.CSharp.Models✕
- Connections
- 5 pairs of types, where a type in NSwag.CodeGeneration.CSharp uses a type in NSwag.CodeGeneration.CSharp.Models.
- The types involved
NSwag.CodeGeneration.CSharp.CSharpClientGenerator→NSwag.CodeGeneration.CSharp.Models.CSharpOperationModelNSwag.CodeGeneration.CSharp.CSharpControllerGenerator→NSwag.CodeGeneration.CSharp.Models.CSharpOperationModelNSwag.CodeGeneration.CSharp.CSharpControllerGeneratorSettings→NSwag.CodeGeneration.CSharp.Models.CSharpControllerRouteNamingStrategyNSwag.CodeGeneration.CSharp.CSharpControllerGeneratorSettings→NSwag.CodeGeneration.CSharp.Models.CSharpControllerStyleNSwag.CodeGeneration.CSharp.CSharpControllerGeneratorSettings→NSwag.CodeGeneration.CSharp.Models.CSharpControllerTarget
- Direction
- NSwag.CodeGeneration.CSharp uses NSwag.CodeGeneration.CSharp.Models, so a change to NSwag.CodeGeneration.CSharp.Models can break NSwag.CodeGeneration.CSharp, while a change to NSwag.CodeGeneration.CSharp can't break NSwag.CodeGeneration.CSharp.Models.
- Position
- Below the diagonal: NSwag.CodeGeneration.CSharp uses a module listed above it, which is the healthy direction.
21→5 NSwag.CodeGeneration.TypeScript uses NSwag✕
- Connections
- 2 pairs of types, where a type in NSwag.CodeGeneration.TypeScript uses a type in NSwag.
- The types involved
NSwag.CodeGeneration.TypeScript.TypeScriptClientGenerator→NSwag.OpenApiDocumentNSwag.CodeGeneration.TypeScript.TypeScriptClientGenerator→NSwag.OpenApiOperation
- Direction
- NSwag.CodeGeneration.TypeScript uses NSwag, so a change to NSwag can break NSwag.CodeGeneration.TypeScript, while a change to NSwag.CodeGeneration.TypeScript can't break NSwag.
- Position
- Below the diagonal: NSwag.CodeGeneration.TypeScript uses a module listed above it, which is the healthy direction.
21→12 NSwag.CodeGeneration.TypeScript uses NSwag.CodeGeneration✕
- Connections
- 4 pairs of types, where a type in NSwag.CodeGeneration.TypeScript uses a type in NSwag.CodeGeneration.
- The types involved
NSwag.CodeGeneration.TypeScript.TypeScriptClientGenerator→NSwag.CodeGeneration.ClientGeneratorBaseNSwag.CodeGeneration.TypeScript.TypeScriptClientGenerator→NSwag.CodeGeneration.ClientGeneratorBaseSettingsNSwag.CodeGeneration.TypeScript.TypeScriptClientGenerator→NSwag.CodeGeneration.ClientGeneratorOutputTypeNSwag.CodeGeneration.TypeScript.TypeScriptClientGeneratorSettings→NSwag.CodeGeneration.ClientGeneratorBaseSettings
- Direction
- NSwag.CodeGeneration.TypeScript uses NSwag.CodeGeneration, so a change to NSwag.CodeGeneration can break NSwag.CodeGeneration.TypeScript, while a change to NSwag.CodeGeneration.TypeScript can't break NSwag.CodeGeneration.
- Position
- Below the diagonal: NSwag.CodeGeneration.TypeScript uses a module listed above it, which is the healthy direction.
21→18 NSwag.CodeGeneration.TypeScript uses NSwag.CodeGeneration.TypeScript.Models✕
- Connections
- 2 pairs of types, where a type in NSwag.CodeGeneration.TypeScript uses a type in NSwag.CodeGeneration.TypeScript.Models.
- The types involved
NSwag.CodeGeneration.TypeScript.TypeScriptClientGenerator→NSwag.CodeGeneration.TypeScript.Models.TypeScriptOperationModelNSwag.CodeGeneration.TypeScript.TypeScriptClientGenerator→NSwag.CodeGeneration.TypeScript.Models.TypeScriptResponseModel
- Direction
- NSwag.CodeGeneration.TypeScript uses NSwag.CodeGeneration.TypeScript.Models, so a change to NSwag.CodeGeneration.TypeScript.Models can break NSwag.CodeGeneration.TypeScript, while a change to NSwag.CodeGeneration.TypeScript can't break NSwag.CodeGeneration.TypeScript.Models.
- Position
- Below the diagonal: NSwag.CodeGeneration.TypeScript uses a module listed above it, which is the healthy direction.
22→5 NSwag.Generation.AspNetCore uses NSwag✕
- Connections
- 6 pairs of types, where a type in NSwag.Generation.AspNetCore uses a type in NSwag.
- The types involved
NSwag.Generation.AspNetCore.AspNetCoreOpenApiDocumentGenerator→NSwag.OpenApiDocumentNSwag.Generation.AspNetCore.AspNetCoreOpenApiDocumentGenerator→NSwag.OpenApiOperationDescriptionNSwag.Generation.AspNetCore.AspNetCoreOpenApiDocumentGenerator→NSwag.OpenApiSchemaResolverNSwag.Generation.AspNetCore.AspNetCoreOpenApiDocumentGeneratorSettings→NSwag.OpenApiDocumentNSwag.Generation.AspNetCore.AspNetCoreOperationProcessorContext→NSwag.OpenApiDocumentNSwag.Generation.AspNetCore.AspNetCoreOperationProcessorContext→NSwag.OpenApiOperationDescription
- Direction
- NSwag.Generation.AspNetCore uses NSwag, so a change to NSwag can break NSwag.Generation.AspNetCore, while a change to NSwag.Generation.AspNetCore can't break NSwag.
- Position
- Below the diagonal: NSwag.Generation.AspNetCore uses a module listed above it, which is the healthy direction.
22→11 NSwag.Generation.AspNetCore uses NSwag.Generation.Processors.Contexts✕
- Connections
- 1 pair of types, where a type in NSwag.Generation.AspNetCore uses a type in NSwag.Generation.Processors.Contexts.
- The types involved
NSwag.Generation.AspNetCore.AspNetCoreOperationProcessorContext→NSwag.Generation.Processors.Contexts.OperationProcessorContext
- Direction
- NSwag.Generation.AspNetCore uses NSwag.Generation.Processors.Contexts, so a change to NSwag.Generation.Processors.Contexts can break NSwag.Generation.AspNetCore, while a change to NSwag.Generation.AspNetCore can't break NSwag.Generation.Processors.Contexts.
- Position
- Below the diagonal: NSwag.Generation.AspNetCore uses a module listed above it, which is the healthy direction.
22→19 NSwag.Generation.AspNetCore uses NSwag.Generation✕
- Connections
- 4 pairs of types, where a type in NSwag.Generation.AspNetCore uses a type in NSwag.Generation.
- The types involved
NSwag.Generation.AspNetCore.AspNetCoreOpenApiDocumentGenerator→NSwag.Generation.OpenApiDocumentGeneratorNSwag.Generation.AspNetCore.AspNetCoreOpenApiDocumentGeneratorSettings→NSwag.Generation.OpenApiDocumentGeneratorSettingsNSwag.Generation.AspNetCore.AspNetCoreOperationProcessorContext→NSwag.Generation.OpenApiDocumentGeneratorNSwag.Generation.AspNetCore.AspNetCoreOperationProcessorContext→NSwag.Generation.OpenApiDocumentGeneratorSettings
- Direction
- NSwag.Generation.AspNetCore uses NSwag.Generation, so a change to NSwag.Generation can break NSwag.Generation.AspNetCore, while a change to NSwag.Generation.AspNetCore can't break NSwag.Generation.
- Position
- Below the diagonal: NSwag.Generation.AspNetCore uses a module listed above it, which is the healthy direction.
23→4 NSwag.Generation.WebApi uses NSwag.Generation.WebApi.Infrastructure✕
- Connections
- 2 pairs of types, where a type in NSwag.Generation.WebApi uses a type in NSwag.Generation.WebApi.Infrastructure.
- The types involved
NSwag.Generation.WebApi.WebApiOpenApiDocumentGenerator→NSwag.Generation.WebApi.Infrastructure.RouteAttributeFacadeNSwag.Generation.WebApi.WebApiOpenApiDocumentGenerator→NSwag.Generation.WebApi.Infrastructure.RoutePrefixAttributeFacade
- Direction
- NSwag.Generation.WebApi uses NSwag.Generation.WebApi.Infrastructure, so a change to NSwag.Generation.WebApi.Infrastructure can break NSwag.Generation.WebApi, while a change to NSwag.Generation.WebApi can't break NSwag.Generation.WebApi.Infrastructure.
- Position
- Below the diagonal: NSwag.Generation.WebApi uses a module listed above it, which is the healthy direction.
23→5 NSwag.Generation.WebApi uses NSwag✕
- Connections
- 3 pairs of types, where a type in NSwag.Generation.WebApi uses a type in NSwag.
- The types involved
NSwag.Generation.WebApi.WebApiOpenApiDocumentGenerator→NSwag.OpenApiDocumentNSwag.Generation.WebApi.WebApiOpenApiDocumentGenerator→NSwag.OpenApiOperationDescriptionNSwag.Generation.WebApi.WebApiOpenApiDocumentGenerator→NSwag.OpenApiSchemaResolver
- Direction
- NSwag.Generation.WebApi uses NSwag, so a change to NSwag can break NSwag.Generation.WebApi, while a change to NSwag.Generation.WebApi can't break NSwag.
- Position
- Below the diagonal: NSwag.Generation.WebApi uses a module listed above it, which is the healthy direction.
23→19 NSwag.Generation.WebApi uses NSwag.Generation✕
- Connections
- 2 pairs of types, where a type in NSwag.Generation.WebApi uses a type in NSwag.Generation.
- The types involved
NSwag.Generation.WebApi.WebApiOpenApiDocumentGenerator→NSwag.Generation.OpenApiDocumentGeneratorNSwag.Generation.WebApi.WebApiOpenApiDocumentGeneratorSettings→NSwag.Generation.OpenApiDocumentGeneratorSettings
- Direction
- NSwag.Generation.WebApi uses NSwag.Generation, so a change to NSwag.Generation can break NSwag.Generation.WebApi, while a change to NSwag.Generation.WebApi can't break NSwag.Generation.
- Position
- Below the diagonal: NSwag.Generation.WebApi uses a module listed above it, which is the healthy direction.
24→5 Microsoft.Extensions.DependencyInjection uses NSwag✕
- Connections
- 1 pair of types, where a type in Microsoft.Extensions.DependencyInjection uses a type in NSwag.
- The types involved
Microsoft.Extensions.DependencyInjection.NSwagSwaggerGeneratorSettingsExtensions→NSwag.OpenApiSecurityScheme
- Direction
- Microsoft.Extensions.DependencyInjection uses NSwag, so a change to NSwag can break Microsoft.Extensions.DependencyInjection, while a change to Microsoft.Extensions.DependencyInjection can't break NSwag.
- Position
- Below the diagonal: Microsoft.Extensions.DependencyInjection uses a module listed above it, which is the healthy direction.
24→19 Microsoft.Extensions.DependencyInjection uses NSwag.Generation✕
- Connections
- 1 pair of types, where a type in Microsoft.Extensions.DependencyInjection uses a type in NSwag.Generation.
- The types involved
Microsoft.Extensions.DependencyInjection.NSwagSwaggerGeneratorSettingsExtensions→NSwag.Generation.OpenApiDocumentGeneratorSettings
- Direction
- Microsoft.Extensions.DependencyInjection uses NSwag.Generation, so a change to NSwag.Generation can break Microsoft.Extensions.DependencyInjection, while a change to Microsoft.Extensions.DependencyInjection can't break NSwag.Generation.
- Position
- Below the diagonal: Microsoft.Extensions.DependencyInjection uses a module listed above it, which is the healthy direction.
24→22 Microsoft.Extensions.DependencyInjection uses NSwag.Generation.AspNetCore✕
- Connections
- 1 pair of types, where a type in Microsoft.Extensions.DependencyInjection uses a type in NSwag.Generation.AspNetCore.
- The types involved
Microsoft.Extensions.DependencyInjection.NSwagServiceCollectionExtensions→NSwag.Generation.AspNetCore.AspNetCoreOpenApiDocumentGeneratorSettings
- Direction
- Microsoft.Extensions.DependencyInjection uses NSwag.Generation.AspNetCore, so a change to NSwag.Generation.AspNetCore can break Microsoft.Extensions.DependencyInjection, while a change to Microsoft.Extensions.DependencyInjection can't break NSwag.Generation.AspNetCore.
- Position
- Below the diagonal: Microsoft.Extensions.DependencyInjection uses a module listed above it, which is the healthy direction.
25→5 NSwag.AspNet.Owin uses NSwag✕
- Connections
- 1 pair of types, where a type in NSwag.AspNet.Owin uses a type in NSwag.
- The types involved
NSwag.AspNet.Owin.SwaggerSettings→NSwag.OpenApiDocument
- Direction
- NSwag.AspNet.Owin uses NSwag, so a change to NSwag can break NSwag.AspNet.Owin, while a change to NSwag.AspNet.Owin can't break NSwag.
- Position
- Below the diagonal: NSwag.AspNet.Owin uses a module listed above it, which is the healthy direction.
25→23 NSwag.AspNet.Owin uses NSwag.Generation.WebApi✕
- Connections
- 1 pair of types, where a type in NSwag.AspNet.Owin uses a type in NSwag.Generation.WebApi.
- The types involved
NSwag.AspNet.Owin.SwaggerExtensions→NSwag.Generation.WebApi.WebApiOpenApiDocumentGeneratorSettings
- Direction
- NSwag.AspNet.Owin uses NSwag.Generation.WebApi, so a change to NSwag.Generation.WebApi can break NSwag.AspNet.Owin, while a change to NSwag.AspNet.Owin can't break NSwag.Generation.WebApi.
- Position
- Below the diagonal: NSwag.AspNet.Owin uses a module listed above it, which is the healthy direction.
26→1 NSwag.AspNetCore uses Microsoft.Extensions.ApiDescriptions✕
- Connections
- 1 pair of types, where a type in NSwag.AspNetCore uses a type in Microsoft.Extensions.ApiDescriptions.
- The types involved
NSwag.AspNetCore.OpenApiDocumentProvider→Microsoft.Extensions.ApiDescriptions.IDocumentProvider
- Direction
- NSwag.AspNetCore uses Microsoft.Extensions.ApiDescriptions, so a change to Microsoft.Extensions.ApiDescriptions can break NSwag.AspNetCore, while a change to NSwag.AspNetCore can't break Microsoft.Extensions.ApiDescriptions.
- Position
- Below the diagonal: NSwag.AspNetCore uses a module listed above it, which is the healthy direction.
26→5 NSwag.AspNetCore uses NSwag✕
- Connections
- 2 pairs of types, where a type in NSwag.AspNetCore uses a type in NSwag.
- The types involved
NSwag.AspNetCore.OpenApiDocumentMiddlewareSettings→NSwag.OpenApiDocumentNSwag.AspNetCore.OpenApiDocumentProvider→NSwag.OpenApiDocument
- Direction
- NSwag.AspNetCore uses NSwag, so a change to NSwag can break NSwag.AspNetCore, while a change to NSwag.AspNetCore can't break NSwag.
- Position
- Below the diagonal: NSwag.AspNetCore uses a module listed above it, which is the healthy direction.
26→19 NSwag.AspNetCore uses NSwag.Generation✕
- Connections
- 1 pair of types, where a type in NSwag.AspNetCore uses a type in NSwag.Generation.
- The types involved
NSwag.AspNetCore.OpenApiDocumentProvider→NSwag.Generation.IOpenApiDocumentGenerator
- Direction
- NSwag.AspNetCore uses NSwag.Generation, so a change to NSwag.Generation can break NSwag.AspNetCore, while a change to NSwag.AspNetCore can't break NSwag.Generation.
- Position
- Below the diagonal: NSwag.AspNetCore uses a module listed above it, which is the healthy direction.
26→22 NSwag.AspNetCore uses NSwag.Generation.AspNetCore✕
- Connections
- 1 pair of types, where a type in NSwag.AspNetCore uses a type in NSwag.Generation.AspNetCore.
- The types involved
NSwag.AspNetCore.OpenApiDocumentRegistration→NSwag.Generation.AspNetCore.AspNetCoreOpenApiDocumentGeneratorSettings
- Direction
- NSwag.AspNetCore uses NSwag.Generation.AspNetCore, so a change to NSwag.Generation.AspNetCore can break NSwag.AspNetCore, while a change to NSwag.AspNetCore can't break NSwag.Generation.AspNetCore.
- Position
- Below the diagonal: NSwag.AspNetCore uses a module listed above it, which is the healthy direction.
27→2 NSwag.Commands.CodeGeneration uses NConsole✕
- Connections
- 12 pairs of types, where a type in NSwag.Commands.CodeGeneration uses a type in NConsole.
- The types involved
NSwag.Commands.CodeGeneration.JsonSchemaToCSharpCommand→NConsole.CommandLineProcessorNSwag.Commands.CodeGeneration.JsonSchemaToCSharpCommand→NConsole.IConsoleHostNSwag.Commands.CodeGeneration.JsonSchemaToOpenApiCommand→NConsole.CommandLineProcessorNSwag.Commands.CodeGeneration.JsonSchemaToOpenApiCommand→NConsole.IConsoleHostNSwag.Commands.CodeGeneration.JsonSchemaToTypeScriptCommand→NConsole.CommandLineProcessorNSwag.Commands.CodeGeneration.JsonSchemaToTypeScriptCommand→NConsole.IConsoleHostNSwag.Commands.CodeGeneration.OpenApiToCSharpClientCommand→NConsole.CommandLineProcessorNSwag.Commands.CodeGeneration.OpenApiToCSharpClientCommand→NConsole.IConsoleHostNSwag.Commands.CodeGeneration.OpenApiToCSharpControllerCommand→NConsole.CommandLineProcessorNSwag.Commands.CodeGeneration.OpenApiToCSharpControllerCommand→NConsole.IConsoleHostNSwag.Commands.CodeGeneration.OpenApiToTypeScriptClientCommand→NConsole.CommandLineProcessorNSwag.Commands.CodeGeneration.OpenApiToTypeScriptClientCommand→NConsole.IConsoleHost
- Direction
- NSwag.Commands.CodeGeneration uses NConsole, so a change to NConsole can break NSwag.Commands.CodeGeneration, while a change to NSwag.Commands.CodeGeneration can't break NConsole.
- Position
- Below the diagonal: NSwag.Commands.CodeGeneration uses a module listed above it, which is the healthy direction.
27→5 NSwag.Commands.CodeGeneration uses NSwag✕
- Connections
- 1 pair of types, where a type in NSwag.Commands.CodeGeneration uses a type in NSwag.
- The types involved
NSwag.Commands.CodeGeneration.JsonSchemaToOpenApiCommand→NSwag.OpenApiDocument
- Direction
- NSwag.Commands.CodeGeneration uses NSwag, so a change to NSwag can break NSwag.Commands.CodeGeneration, while a change to NSwag.Commands.CodeGeneration can't break NSwag.
- Position
- Below the diagonal: NSwag.Commands.CodeGeneration uses a module listed above it, which is the healthy direction.
27→17 NSwag.Commands.CodeGeneration uses NSwag.CodeGeneration.CSharp.Models✕
- Connections
- 3 pairs of types, where a type in NSwag.Commands.CodeGeneration uses a type in NSwag.CodeGeneration.CSharp.Models.
- The types involved
NSwag.Commands.CodeGeneration.OpenApiToCSharpControllerCommand→NSwag.CodeGeneration.CSharp.Models.CSharpControllerRouteNamingStrategyNSwag.Commands.CodeGeneration.OpenApiToCSharpControllerCommand→NSwag.CodeGeneration.CSharp.Models.CSharpControllerStyleNSwag.Commands.CodeGeneration.OpenApiToCSharpControllerCommand→NSwag.CodeGeneration.CSharp.Models.CSharpControllerTarget
- Direction
- NSwag.Commands.CodeGeneration uses NSwag.CodeGeneration.CSharp.Models, so a change to NSwag.CodeGeneration.CSharp.Models can break NSwag.Commands.CodeGeneration, while a change to NSwag.Commands.CodeGeneration can't break NSwag.CodeGeneration.CSharp.Models.
- Position
- Below the diagonal: NSwag.Commands.CodeGeneration uses a module listed above it, which is the healthy direction.
27→20 NSwag.Commands.CodeGeneration uses NSwag.CodeGeneration.CSharp✕
- Connections
- 1 pair of types, where a type in NSwag.Commands.CodeGeneration uses a type in NSwag.CodeGeneration.CSharp.
- The types involved
NSwag.Commands.CodeGeneration.OpenApiToCSharpClientCommand→NSwag.CodeGeneration.CSharp.CSharpClientGenerator
- Direction
- NSwag.Commands.CodeGeneration uses NSwag.CodeGeneration.CSharp, so a change to NSwag.CodeGeneration.CSharp can break NSwag.Commands.CodeGeneration, while a change to NSwag.Commands.CodeGeneration can't break NSwag.CodeGeneration.CSharp.
- Position
- Below the diagonal: NSwag.Commands.CodeGeneration uses a module listed above it, which is the healthy direction.
27→21 NSwag.Commands.CodeGeneration uses NSwag.CodeGeneration.TypeScript✕
- Connections
- 4 pairs of types, where a type in NSwag.Commands.CodeGeneration uses a type in NSwag.CodeGeneration.TypeScript.
- The types involved
NSwag.Commands.CodeGeneration.OpenApiToTypeScriptClientCommand→NSwag.CodeGeneration.TypeScript.HttpClassNSwag.Commands.CodeGeneration.OpenApiToTypeScriptClientCommand→NSwag.CodeGeneration.TypeScript.InjectionTokenTypeNSwag.Commands.CodeGeneration.OpenApiToTypeScriptClientCommand→NSwag.CodeGeneration.TypeScript.PromiseTypeNSwag.Commands.CodeGeneration.OpenApiToTypeScriptClientCommand→NSwag.CodeGeneration.TypeScript.TypeScriptTemplate
- Direction
- NSwag.Commands.CodeGeneration uses NSwag.CodeGeneration.TypeScript, so a change to NSwag.CodeGeneration.TypeScript can break NSwag.Commands.CodeGeneration, while a change to NSwag.Commands.CodeGeneration can't break NSwag.CodeGeneration.TypeScript.
- Position
- Below the diagonal: NSwag.Commands.CodeGeneration uses a module listed above it, which is the healthy direction.
27→33 NSwag.Commands.CodeGeneration uses NSwag.Commands part of a loop✕
- Connections
- 4 pairs of types, where a type in NSwag.Commands.CodeGeneration uses a type in NSwag.Commands.
- The types involved
NSwag.Commands.CodeGeneration.CodeGeneratorCommandBase→NSwag.Commands.InputOutputCommandBaseNSwag.Commands.CodeGeneration.JsonSchemaToCSharpCommand→NSwag.Commands.InputOutputCommandBaseNSwag.Commands.CodeGeneration.JsonSchemaToOpenApiCommand→NSwag.Commands.OutputCommandBaseNSwag.Commands.CodeGeneration.JsonSchemaToTypeScriptCommand→NSwag.Commands.InputOutputCommandBase
- Direction
- NSwag.Commands.CodeGeneration uses NSwag.Commands, so a change to NSwag.Commands can break NSwag.Commands.CodeGeneration, while a change to NSwag.Commands.CodeGeneration can't break NSwag.Commands.
- 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.
28→5 NSwag.Generation.AspNetCore.Processors uses NSwag✕
- Connections
- 2 pairs of types, where a type in NSwag.Generation.AspNetCore.Processors uses a type in NSwag.
- The types involved
NSwag.Generation.AspNetCore.Processors.OperationParameterProcessor→NSwag.OpenApiOperationDescriptionNSwag.Generation.AspNetCore.Processors.OperationParameterProcessor→NSwag.OpenApiParameter
- Direction
- NSwag.Generation.AspNetCore.Processors uses NSwag, so a change to NSwag can break NSwag.Generation.AspNetCore.Processors, while a change to NSwag.Generation.AspNetCore.Processors can't break NSwag.
- Position
- Below the diagonal: NSwag.Generation.AspNetCore.Processors uses a module listed above it, which is the healthy direction.
28→11 NSwag.Generation.AspNetCore.Processors uses NSwag.Generation.Processors.Contexts✕
- Connections
- 3 pairs of types, where a type in NSwag.Generation.AspNetCore.Processors uses a type in NSwag.Generation.Processors.Contexts.
- The types involved
NSwag.Generation.AspNetCore.Processors.AspNetCoreOperationTagsProcessor→NSwag.Generation.Processors.Contexts.OperationProcessorContextNSwag.Generation.AspNetCore.Processors.OperationParameterProcessor→NSwag.Generation.Processors.Contexts.OperationProcessorContextNSwag.Generation.AspNetCore.Processors.OperationResponseProcessor→NSwag.Generation.Processors.Contexts.OperationProcessorContext
- Direction
- NSwag.Generation.AspNetCore.Processors uses NSwag.Generation.Processors.Contexts, so a change to NSwag.Generation.Processors.Contexts can break NSwag.Generation.AspNetCore.Processors, while a change to NSwag.Generation.AspNetCore.Processors can't break NSwag.Generation.Processors.Contexts.
- Position
- Below the diagonal: NSwag.Generation.AspNetCore.Processors uses a module listed above it, which is the healthy direction.
28→13 NSwag.Generation.AspNetCore.Processors uses NSwag.Generation.Processors✕
- Connections
- 4 pairs of types, where a type in NSwag.Generation.AspNetCore.Processors uses a type in NSwag.Generation.Processors.
- The types involved
NSwag.Generation.AspNetCore.Processors.AspNetCoreOperationTagsProcessor→NSwag.Generation.Processors.OperationTagsProcessorNSwag.Generation.AspNetCore.Processors.OperationParameterProcessor→NSwag.Generation.Processors.IOperationProcessorNSwag.Generation.AspNetCore.Processors.OperationResponseProcessor→NSwag.Generation.Processors.IOperationProcessorNSwag.Generation.AspNetCore.Processors.OperationResponseProcessor→NSwag.Generation.Processors.OperationResponseProcessorBase
- Direction
- NSwag.Generation.AspNetCore.Processors uses NSwag.Generation.Processors, so a change to NSwag.Generation.Processors can break NSwag.Generation.AspNetCore.Processors, while a change to NSwag.Generation.AspNetCore.Processors can't break NSwag.Generation.Processors.
- Position
- Below the diagonal: NSwag.Generation.AspNetCore.Processors uses a module listed above it, which is the healthy direction.
28→22 NSwag.Generation.AspNetCore.Processors uses NSwag.Generation.AspNetCore✕
- Connections
- 2 pairs of types, where a type in NSwag.Generation.AspNetCore.Processors uses a type in NSwag.Generation.AspNetCore.
- The types involved
NSwag.Generation.AspNetCore.Processors.OperationParameterProcessor→NSwag.Generation.AspNetCore.AspNetCoreOpenApiDocumentGeneratorSettingsNSwag.Generation.AspNetCore.Processors.OperationResponseProcessor→NSwag.Generation.AspNetCore.AspNetCoreOpenApiDocumentGeneratorSettings
- Direction
- NSwag.Generation.AspNetCore.Processors uses NSwag.Generation.AspNetCore, so a change to NSwag.Generation.AspNetCore can break NSwag.Generation.AspNetCore.Processors, while a change to NSwag.Generation.AspNetCore.Processors can't break NSwag.Generation.AspNetCore.
- Position
- Below the diagonal: NSwag.Generation.AspNetCore.Processors uses a module listed above it, which is the healthy direction.
29→5 NSwag.Generation.WebApi.Processors uses NSwag✕
- Connections
- 2 pairs of types, where a type in NSwag.Generation.WebApi.Processors uses a type in NSwag.
- The types involved
NSwag.Generation.WebApi.Processors.OperationParameterProcessor→NSwag.OpenApiOperationDescriptionNSwag.Generation.WebApi.Processors.OperationParameterProcessor→NSwag.OpenApiParameter
- Direction
- NSwag.Generation.WebApi.Processors uses NSwag, so a change to NSwag can break NSwag.Generation.WebApi.Processors, while a change to NSwag.Generation.WebApi.Processors can't break NSwag.
- Position
- Below the diagonal: NSwag.Generation.WebApi.Processors uses a module listed above it, which is the healthy direction.
29→11 NSwag.Generation.WebApi.Processors uses NSwag.Generation.Processors.Contexts✕
- Connections
- 3 pairs of types, where a type in NSwag.Generation.WebApi.Processors uses a type in NSwag.Generation.Processors.Contexts.
- The types involved
NSwag.Generation.WebApi.Processors.OperationConsumesProcessor→NSwag.Generation.Processors.Contexts.OperationProcessorContextNSwag.Generation.WebApi.Processors.OperationParameterProcessor→NSwag.Generation.Processors.Contexts.OperationProcessorContextNSwag.Generation.WebApi.Processors.OperationResponseProcessor→NSwag.Generation.Processors.Contexts.OperationProcessorContext
- Direction
- NSwag.Generation.WebApi.Processors uses NSwag.Generation.Processors.Contexts, so a change to NSwag.Generation.Processors.Contexts can break NSwag.Generation.WebApi.Processors, while a change to NSwag.Generation.WebApi.Processors can't break NSwag.Generation.Processors.Contexts.
- Position
- Below the diagonal: NSwag.Generation.WebApi.Processors uses a module listed above it, which is the healthy direction.
29→13 NSwag.Generation.WebApi.Processors uses NSwag.Generation.Processors✕
- Connections
- 4 pairs of types, where a type in NSwag.Generation.WebApi.Processors uses a type in NSwag.Generation.Processors.
- The types involved
NSwag.Generation.WebApi.Processors.OperationConsumesProcessor→NSwag.Generation.Processors.IOperationProcessorNSwag.Generation.WebApi.Processors.OperationParameterProcessor→NSwag.Generation.Processors.IOperationProcessorNSwag.Generation.WebApi.Processors.OperationResponseProcessor→NSwag.Generation.Processors.IOperationProcessorNSwag.Generation.WebApi.Processors.OperationResponseProcessor→NSwag.Generation.Processors.OperationResponseProcessorBase
- Direction
- NSwag.Generation.WebApi.Processors uses NSwag.Generation.Processors, so a change to NSwag.Generation.Processors can break NSwag.Generation.WebApi.Processors, while a change to NSwag.Generation.WebApi.Processors can't break NSwag.Generation.Processors.
- Position
- Below the diagonal: NSwag.Generation.WebApi.Processors uses a module listed above it, which is the healthy direction.
29→23 NSwag.Generation.WebApi.Processors uses NSwag.Generation.WebApi✕
- Connections
- 2 pairs of types, where a type in NSwag.Generation.WebApi.Processors uses a type in NSwag.Generation.WebApi.
- The types involved
NSwag.Generation.WebApi.Processors.OperationParameterProcessor→NSwag.Generation.WebApi.WebApiOpenApiDocumentGeneratorSettingsNSwag.Generation.WebApi.Processors.OperationResponseProcessor→NSwag.Generation.WebApi.WebApiOpenApiDocumentGeneratorSettings
- Direction
- NSwag.Generation.WebApi.Processors uses NSwag.Generation.WebApi, so a change to NSwag.Generation.WebApi can break NSwag.Generation.WebApi.Processors, while a change to NSwag.Generation.WebApi.Processors can't break NSwag.Generation.WebApi.
- Position
- Below the diagonal: NSwag.Generation.WebApi.Processors uses a module listed above it, which is the healthy direction.
30→26 Microsoft.AspNetCore.Builder uses NSwag.AspNetCore✕
- Connections
- 6 pairs of types, where a type in Microsoft.AspNetCore.Builder uses a type in NSwag.AspNetCore.
- The types involved
Microsoft.AspNetCore.Builder.NSwagApplicationBuilderExtensions→NSwag.AspNetCore.ApimundoUiSettingsMicrosoft.AspNetCore.Builder.NSwagApplicationBuilderExtensions→NSwag.AspNetCore.OpenApiDocumentMiddlewareSettingsMicrosoft.AspNetCore.Builder.NSwagApplicationBuilderExtensions→NSwag.AspNetCore.OpenApiDocumentRegistrationMicrosoft.AspNetCore.Builder.NSwagApplicationBuilderExtensions→NSwag.AspNetCore.ReDocSettingsMicrosoft.AspNetCore.Builder.NSwagApplicationBuilderExtensions→NSwag.AspNetCore.SwaggerUiSettingsMicrosoft.AspNetCore.Builder.NSwagApplicationBuilderExtensions→NSwag.AspNetCore.SwaggerUiSettingsBase
- Direction
- Microsoft.AspNetCore.Builder uses NSwag.AspNetCore, so a change to NSwag.AspNetCore can break Microsoft.AspNetCore.Builder, while a change to Microsoft.AspNetCore.Builder can't break NSwag.AspNetCore.
- Position
- Below the diagonal: Microsoft.AspNetCore.Builder uses a module listed above it, which is the healthy direction.
31→23 NSwag.AspNet.Owin.Middlewares uses NSwag.Generation.WebApi✕
- Connections
- 1 pair of types, where a type in NSwag.AspNet.Owin.Middlewares uses a type in NSwag.Generation.WebApi.
- The types involved
NSwag.AspNet.Owin.Middlewares.OpenApiDocumentMiddleware→NSwag.Generation.WebApi.WebApiOpenApiDocumentGeneratorSettings
- Direction
- NSwag.AspNet.Owin.Middlewares uses NSwag.Generation.WebApi, so a change to NSwag.Generation.WebApi can break NSwag.AspNet.Owin.Middlewares, while a change to NSwag.AspNet.Owin.Middlewares can't break NSwag.Generation.WebApi.
- Position
- Below the diagonal: NSwag.AspNet.Owin.Middlewares uses a module listed above it, which is the healthy direction.
31→25 NSwag.AspNet.Owin.Middlewares uses NSwag.AspNet.Owin✕
- Connections
- 2 pairs of types, where a type in NSwag.AspNet.Owin.Middlewares uses a type in NSwag.AspNet.Owin.
- The types involved
NSwag.AspNet.Owin.Middlewares.OpenApiDocumentMiddleware→NSwag.AspNet.Owin.SwaggerSettingsNSwag.AspNet.Owin.Middlewares.SwaggerUiIndexMiddleware→NSwag.AspNet.Owin.SwaggerUiSettingsBase
- Direction
- NSwag.AspNet.Owin.Middlewares uses NSwag.AspNet.Owin, so a change to NSwag.AspNet.Owin can break NSwag.AspNet.Owin.Middlewares, while a change to NSwag.AspNet.Owin.Middlewares can't break NSwag.AspNet.Owin.
- Position
- Below the diagonal: NSwag.AspNet.Owin.Middlewares uses a module listed above it, which is the healthy direction.
32→5 NSwag.AspNetCore.Middlewares uses NSwag✕
- Connections
- 1 pair of types, where a type in NSwag.AspNetCore.Middlewares uses a type in NSwag.
- The types involved
NSwag.AspNetCore.Middlewares.OpenApiDocumentMiddleware→NSwag.OpenApiDocument
- Direction
- NSwag.AspNetCore.Middlewares uses NSwag, so a change to NSwag can break NSwag.AspNetCore.Middlewares, while a change to NSwag.AspNetCore.Middlewares can't break NSwag.
- Position
- Below the diagonal: NSwag.AspNetCore.Middlewares uses a module listed above it, which is the healthy direction.
32→26 NSwag.AspNetCore.Middlewares uses NSwag.AspNetCore✕
- Connections
- 3 pairs of types, where a type in NSwag.AspNetCore.Middlewares uses a type in NSwag.AspNetCore.
- The types involved
NSwag.AspNetCore.Middlewares.OpenApiDocumentMiddleware→NSwag.AspNetCore.OpenApiDocumentMiddlewareSettingsNSwag.AspNetCore.Middlewares.OpenApiDocumentMiddleware→NSwag.AspNetCore.OpenApiDocumentProviderNSwag.AspNetCore.Middlewares.SwaggerUiIndexMiddleware→NSwag.AspNetCore.SwaggerUiSettingsBase
- Direction
- NSwag.AspNetCore.Middlewares uses NSwag.AspNetCore, so a change to NSwag.AspNetCore can break NSwag.AspNetCore.Middlewares, while a change to NSwag.AspNetCore.Middlewares can't break NSwag.AspNetCore.
- Position
- Below the diagonal: NSwag.AspNetCore.Middlewares uses a module listed above it, which is the healthy direction.
33→2 NSwag.Commands uses NConsole✕
- Connections
- 5 pairs of types, where a type in NSwag.Commands uses a type in NConsole.
- The types involved
NSwag.Commands.IOutputCommand→NConsole.IConsoleCommandNSwag.Commands.NSwagCommandProcessor→NConsole.IConsoleHostNSwag.Commands.OutputCommandBase→NConsole.CommandLineProcessorNSwag.Commands.OutputCommandBase→NConsole.IConsoleHostNSwag.Commands.OutputCommandExtensions→NConsole.IConsoleHost
- Direction
- NSwag.Commands uses NConsole, so a change to NConsole can break NSwag.Commands, while a change to NSwag.Commands can't break NConsole.
- Position
- Below the diagonal: NSwag.Commands uses a module listed above it, which is the healthy direction.
33→5 NSwag.Commands uses NSwag✕
- Connections
- 4 pairs of types, where a type in NSwag.Commands uses a type in NSwag.
- The types involved
NSwag.Commands.InputOutputCommandBase→NSwag.OpenApiDocumentNSwag.Commands.NSwagDocumentBase→NSwag.OpenApiDocumentNSwag.Commands.OutputCommandBase→NSwag.OpenApiDocumentNSwag.Commands.OutputCommandExtensions→NSwag.OpenApiDocument
- Direction
- NSwag.Commands uses NSwag, so a change to NSwag can break NSwag.Commands, while a change to NSwag.Commands can't break NSwag.
- Position
- Below the diagonal: NSwag.Commands uses a module listed above it, which is the healthy direction.
33→8 NSwag.Commands uses NSwag.CodeGeneration.OperationNameGenerators✕
- Connections
- 1 pair of types, where a type in NSwag.Commands uses a type in NSwag.CodeGeneration.OperationNameGenerators.
- The types involved
NSwag.Commands.OperationGenerationModeConverter→NSwag.CodeGeneration.OperationNameGenerators.IOperationNameGenerator
- Direction
- NSwag.Commands uses NSwag.CodeGeneration.OperationNameGenerators, so a change to NSwag.CodeGeneration.OperationNameGenerators can break NSwag.Commands, while a change to NSwag.Commands can't break NSwag.CodeGeneration.OperationNameGenerators.
- Position
- Below the diagonal: NSwag.Commands uses a module listed above it, which is the healthy direction.
33→9 NSwag.Commands uses NSwag.Commands.Generation✕
- Connections
- 1 pair of types, where a type in NSwag.Commands uses a type in NSwag.Commands.Generation.
- The types involved
NSwag.Commands.OpenApiGeneratorCollection→NSwag.Commands.Generation.FromDocumentCommand
- Direction
- NSwag.Commands uses NSwag.Commands.Generation, so a change to NSwag.Commands.Generation can break NSwag.Commands, while a change to NSwag.Commands can't break NSwag.Commands.Generation.
- Position
- Below the diagonal: NSwag.Commands uses a module listed above it, which is the healthy direction.
33→10 NSwag.Commands uses NSwag.Commands.Generation.AspNetCore✕
- Connections
- 1 pair of types, where a type in NSwag.Commands uses a type in NSwag.Commands.Generation.AspNetCore.
- The types involved
NSwag.Commands.OpenApiGeneratorCollection→NSwag.Commands.Generation.AspNetCore.AspNetCoreToOpenApiCommand
- Direction
- NSwag.Commands uses NSwag.Commands.Generation.AspNetCore, so a change to NSwag.Commands.Generation.AspNetCore can break NSwag.Commands, while a change to NSwag.Commands can't break NSwag.Commands.Generation.AspNetCore.
- Position
- Below the diagonal: NSwag.Commands uses a module listed above it, which is the healthy direction.
33→27 NSwag.Commands uses NSwag.Commands.CodeGeneration✕
- Connections
- 5 pairs of types, where a type in NSwag.Commands uses a type in NSwag.Commands.CodeGeneration.
- The types involved
NSwag.Commands.CodeGeneratorCollection→NSwag.Commands.CodeGeneration.OpenApiToCSharpClientCommandNSwag.Commands.CodeGeneratorCollection→NSwag.Commands.CodeGeneration.OpenApiToCSharpControllerCommandNSwag.Commands.CodeGeneratorCollection→NSwag.Commands.CodeGeneration.OpenApiToTypeScriptClientCommandNSwag.Commands.OpenApiGeneratorCollection→NSwag.Commands.CodeGeneration.JsonSchemaToOpenApiCommandNSwag.Commands.OperationGenerationModeConverter→NSwag.Commands.CodeGeneration.OperationGenerationMode
- Direction
- NSwag.Commands uses NSwag.Commands.CodeGeneration, so a change to NSwag.Commands.CodeGeneration can break NSwag.Commands, while a change to NSwag.Commands can't break NSwag.Commands.CodeGeneration.
- Position
- Below the diagonal: NSwag.Commands uses a module listed above it, which is the healthy direction.
34→33 NSwagStudio uses NSwag.Commands✕
- Connections
- 1 pair of types, where a type in NSwagStudio uses a type in NSwag.Commands.
- The types involved
NSwagStudio.ISwaggerGeneratorView→NSwag.Commands.IOutputCommand
- Direction
- NSwagStudio uses NSwag.Commands, so a change to NSwag.Commands can break NSwagStudio, while a change to NSwagStudio can't break NSwag.Commands.
- Position
- Below the diagonal: NSwagStudio uses a module listed above it, which is the healthy direction.
35→5 NSwagStudio.ViewModels.CodeGenerators uses NSwag✕
- Connections
- 1 pair of types, where a type in NSwagStudio.ViewModels.CodeGenerators uses a type in NSwag.
- The types involved
NSwagStudio.ViewModels.CodeGenerators.SwaggerOutputViewModel→NSwag.OpenApiDocument
- Direction
- NSwagStudio.ViewModels.CodeGenerators uses NSwag, so a change to NSwag can break NSwagStudio.ViewModels.CodeGenerators, while a change to NSwagStudio.ViewModels.CodeGenerators can't break NSwag.
- Position
- Below the diagonal: NSwagStudio.ViewModels.CodeGenerators uses a module listed above it, which is the healthy direction.
35→17 NSwagStudio.ViewModels.CodeGenerators uses NSwag.CodeGeneration.CSharp.Models✕
- Connections
- 3 pairs of types, where a type in NSwagStudio.ViewModels.CodeGenerators uses a type in NSwag.CodeGeneration.CSharp.Models.
- The types involved
NSwagStudio.ViewModels.CodeGenerators.SwaggerToCSharpControllerGeneratorViewModel→NSwag.CodeGeneration.CSharp.Models.CSharpControllerRouteNamingStrategyNSwagStudio.ViewModels.CodeGenerators.SwaggerToCSharpControllerGeneratorViewModel→NSwag.CodeGeneration.CSharp.Models.CSharpControllerStyleNSwagStudio.ViewModels.CodeGenerators.SwaggerToCSharpControllerGeneratorViewModel→NSwag.CodeGeneration.CSharp.Models.CSharpControllerTarget
- Direction
- NSwagStudio.ViewModels.CodeGenerators uses NSwag.CodeGeneration.CSharp.Models, so a change to NSwag.CodeGeneration.CSharp.Models can break NSwagStudio.ViewModels.CodeGenerators, while a change to NSwagStudio.ViewModels.CodeGenerators can't break NSwag.CodeGeneration.CSharp.Models.
- Position
- Below the diagonal: NSwagStudio.ViewModels.CodeGenerators uses a module listed above it, which is the healthy direction.
35→21 NSwagStudio.ViewModels.CodeGenerators uses NSwag.CodeGeneration.TypeScript✕
- Connections
- 4 pairs of types, where a type in NSwagStudio.ViewModels.CodeGenerators uses a type in NSwag.CodeGeneration.TypeScript.
- The types involved
NSwagStudio.ViewModels.CodeGenerators.SwaggerToTypeScriptClientGeneratorViewModel→NSwag.CodeGeneration.TypeScript.HttpClassNSwagStudio.ViewModels.CodeGenerators.SwaggerToTypeScriptClientGeneratorViewModel→NSwag.CodeGeneration.TypeScript.InjectionTokenTypeNSwagStudio.ViewModels.CodeGenerators.SwaggerToTypeScriptClientGeneratorViewModel→NSwag.CodeGeneration.TypeScript.PromiseTypeNSwagStudio.ViewModels.CodeGenerators.SwaggerToTypeScriptClientGeneratorViewModel→NSwag.CodeGeneration.TypeScript.TypeScriptTemplate
- Direction
- NSwagStudio.ViewModels.CodeGenerators uses NSwag.CodeGeneration.TypeScript, so a change to NSwag.CodeGeneration.TypeScript can break NSwagStudio.ViewModels.CodeGenerators, while a change to NSwagStudio.ViewModels.CodeGenerators can't break NSwag.CodeGeneration.TypeScript.
- Position
- Below the diagonal: NSwagStudio.ViewModels.CodeGenerators uses a module listed above it, which is the healthy direction.
35→27 NSwagStudio.ViewModels.CodeGenerators uses NSwag.Commands.CodeGeneration✕
- Connections
- 6 pairs of types, where a type in NSwagStudio.ViewModels.CodeGenerators uses a type in NSwag.Commands.CodeGeneration.
- The types involved
NSwagStudio.ViewModels.CodeGenerators.SwaggerToCSharpClientGeneratorViewModel→NSwag.Commands.CodeGeneration.OpenApiToCSharpClientCommandNSwagStudio.ViewModels.CodeGenerators.SwaggerToCSharpClientGeneratorViewModel→NSwag.Commands.CodeGeneration.OperationGenerationModeNSwagStudio.ViewModels.CodeGenerators.SwaggerToCSharpControllerGeneratorViewModel→NSwag.Commands.CodeGeneration.OpenApiToCSharpControllerCommandNSwagStudio.ViewModels.CodeGenerators.SwaggerToCSharpControllerGeneratorViewModel→NSwag.Commands.CodeGeneration.OperationGenerationModeNSwagStudio.ViewModels.CodeGenerators.SwaggerToTypeScriptClientGeneratorViewModel→NSwag.Commands.CodeGeneration.OpenApiToTypeScriptClientCommandNSwagStudio.ViewModels.CodeGenerators.SwaggerToTypeScriptClientGeneratorViewModel→NSwag.Commands.CodeGeneration.OperationGenerationMode
- Direction
- NSwagStudio.ViewModels.CodeGenerators uses NSwag.Commands.CodeGeneration, so a change to NSwag.Commands.CodeGeneration can break NSwagStudio.ViewModels.CodeGenerators, while a change to NSwagStudio.ViewModels.CodeGenerators can't break NSwag.Commands.CodeGeneration.
- Position
- Below the diagonal: NSwagStudio.ViewModels.CodeGenerators uses a module listed above it, which is the healthy direction.
35→33 NSwagStudio.ViewModels.CodeGenerators uses NSwag.Commands✕
- Connections
- 3 pairs of types, where a type in NSwagStudio.ViewModels.CodeGenerators uses a type in NSwag.Commands.
- The types involved
NSwagStudio.ViewModels.CodeGenerators.SwaggerToCSharpClientGeneratorViewModel→NSwag.Commands.NewLineBehaviorNSwagStudio.ViewModels.CodeGenerators.SwaggerToCSharpControllerGeneratorViewModel→NSwag.Commands.NewLineBehaviorNSwagStudio.ViewModels.CodeGenerators.SwaggerToTypeScriptClientGeneratorViewModel→NSwag.Commands.NewLineBehavior
- Direction
- NSwagStudio.ViewModels.CodeGenerators uses NSwag.Commands, so a change to NSwag.Commands can break NSwagStudio.ViewModels.CodeGenerators, while a change to NSwagStudio.ViewModels.CodeGenerators can't break NSwag.Commands.
- Position
- Below the diagonal: NSwagStudio.ViewModels.CodeGenerators uses a module listed above it, which is the healthy direction.
35→37 NSwagStudio.ViewModels.CodeGenerators uses NSwagStudio.ViewModels part of a loop✕
- Connections
- 4 pairs of types, where a type in NSwagStudio.ViewModels.CodeGenerators uses a type in NSwagStudio.ViewModels.
- The types involved
NSwagStudio.ViewModels.CodeGenerators.SwaggerOutputViewModel→NSwagStudio.ViewModels.ViewModelBaseNSwagStudio.ViewModels.CodeGenerators.SwaggerToCSharpClientGeneratorViewModel→NSwagStudio.ViewModels.ViewModelBaseNSwagStudio.ViewModels.CodeGenerators.SwaggerToCSharpControllerGeneratorViewModel→NSwagStudio.ViewModels.ViewModelBaseNSwagStudio.ViewModels.CodeGenerators.SwaggerToTypeScriptClientGeneratorViewModel→NSwagStudio.ViewModels.ViewModelBase
- Direction
- NSwagStudio.ViewModels.CodeGenerators uses NSwagStudio.ViewModels, so a change to NSwagStudio.ViewModels can break NSwagStudio.ViewModels.CodeGenerators, while a change to NSwagStudio.ViewModels.CodeGenerators can't break NSwagStudio.ViewModels.
- 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.
36→33 NSwagStudio.Views.CodeGenerators uses NSwag.Commands✕
- Connections
- 8 pairs of types, where a type in NSwagStudio.Views.CodeGenerators uses a type in NSwag.Commands.
- The types involved
NSwagStudio.Views.CodeGenerators.CodeGeneratorViewBase→NSwag.Commands.OpenApiDocumentExecutionResultNSwagStudio.Views.CodeGenerators.SwaggerOutputView→NSwag.Commands.OpenApiDocumentExecutionResultNSwagStudio.Views.CodeGenerators.SwaggerToCSharpClientGeneratorView→NSwag.Commands.NSwagDocumentNSwagStudio.Views.CodeGenerators.SwaggerToCSharpClientGeneratorView→NSwag.Commands.OpenApiDocumentExecutionResultNSwagStudio.Views.CodeGenerators.SwaggerToCSharpControllerGeneratorView→NSwag.Commands.NSwagDocumentNSwagStudio.Views.CodeGenerators.SwaggerToCSharpControllerGeneratorView→NSwag.Commands.OpenApiDocumentExecutionResultNSwagStudio.Views.CodeGenerators.SwaggerToTypeScriptClientGeneratorView→NSwag.Commands.NSwagDocumentNSwagStudio.Views.CodeGenerators.SwaggerToTypeScriptClientGeneratorView→NSwag.Commands.OpenApiDocumentExecutionResult
- Direction
- NSwagStudio.Views.CodeGenerators uses NSwag.Commands, so a change to NSwag.Commands can break NSwagStudio.Views.CodeGenerators, while a change to NSwagStudio.Views.CodeGenerators can't break NSwag.Commands.
- Position
- Below the diagonal: NSwagStudio.Views.CodeGenerators uses a module listed above it, which is the healthy direction.
36→35 NSwagStudio.Views.CodeGenerators uses NSwagStudio.ViewModels.CodeGenerators✕
- Connections
- 4 pairs of types, where a type in NSwagStudio.Views.CodeGenerators uses a type in NSwagStudio.ViewModels.CodeGenerators.
- The types involved
NSwagStudio.Views.CodeGenerators.SwaggerOutputView→NSwagStudio.ViewModels.CodeGenerators.SwaggerOutputViewModelNSwagStudio.Views.CodeGenerators.SwaggerToCSharpClientGeneratorView→NSwagStudio.ViewModels.CodeGenerators.SwaggerToCSharpClientGeneratorViewModelNSwagStudio.Views.CodeGenerators.SwaggerToCSharpControllerGeneratorView→NSwagStudio.ViewModels.CodeGenerators.SwaggerToCSharpControllerGeneratorViewModelNSwagStudio.Views.CodeGenerators.SwaggerToTypeScriptClientGeneratorView→NSwagStudio.ViewModels.CodeGenerators.SwaggerToTypeScriptClientGeneratorViewModel
- Direction
- NSwagStudio.Views.CodeGenerators uses NSwagStudio.ViewModels.CodeGenerators, so a change to NSwagStudio.ViewModels.CodeGenerators can break NSwagStudio.Views.CodeGenerators, while a change to NSwagStudio.Views.CodeGenerators can't break NSwagStudio.ViewModels.CodeGenerators.
- Position
- Below the diagonal: NSwagStudio.Views.CodeGenerators uses a module listed above it, which is the healthy direction.
37→33 NSwagStudio.ViewModels uses NSwag.Commands✕
- Connections
- 2 pairs of types, where a type in NSwagStudio.ViewModels uses a type in NSwag.Commands.
- The types involved
NSwagStudio.ViewModels.DocumentModel→NSwag.Commands.NSwagDocumentNSwagStudio.ViewModels.DocumentViewModel→NSwag.Commands.Runtime
- Direction
- NSwagStudio.ViewModels uses NSwag.Commands, so a change to NSwag.Commands can break NSwagStudio.ViewModels, while a change to NSwagStudio.ViewModels can't break NSwag.Commands.
- Position
- Below the diagonal: NSwagStudio.ViewModels uses a module listed above it, which is the healthy direction.
37→34 NSwagStudio.ViewModels uses NSwagStudio✕
- Connections
- 1 pair of types, where a type in NSwagStudio.ViewModels uses a type in NSwagStudio.
- The types involved
NSwagStudio.ViewModels.DocumentModel→NSwagStudio.ISwaggerGeneratorView
- Direction
- NSwagStudio.ViewModels uses NSwagStudio, so a change to NSwagStudio can break NSwagStudio.ViewModels, while a change to NSwagStudio.ViewModels can't break NSwagStudio.
- Position
- Below the diagonal: NSwagStudio.ViewModels uses a module listed above it, which is the healthy direction.
37→36 NSwagStudio.ViewModels uses NSwagStudio.Views.CodeGenerators✕
- Connections
- 1 pair of types, where a type in NSwagStudio.ViewModels uses a type in NSwagStudio.Views.CodeGenerators.
- The types involved
NSwagStudio.ViewModels.CodeGeneratorModel→NSwagStudio.Views.CodeGenerators.CodeGeneratorViewBase
- Direction
- NSwagStudio.ViewModels uses NSwagStudio.Views.CodeGenerators, so a change to NSwagStudio.Views.CodeGenerators can break NSwagStudio.ViewModels, while a change to NSwagStudio.ViewModels can't break NSwagStudio.Views.CodeGenerators.
- Position
- Below the diagonal: NSwagStudio.ViewModels uses a module listed above it, which is the healthy direction.
38→9 NSwagStudio.ViewModels.SwaggerGenerators uses NSwag.Commands.Generation✕
- Connections
- 1 pair of types, where a type in NSwagStudio.ViewModels.SwaggerGenerators uses a type in NSwag.Commands.Generation.
- The types involved
NSwagStudio.ViewModels.SwaggerGenerators.SwaggerInputViewModel→NSwag.Commands.Generation.FromDocumentCommand
- Direction
- NSwagStudio.ViewModels.SwaggerGenerators uses NSwag.Commands.Generation, so a change to NSwag.Commands.Generation can break NSwagStudio.ViewModels.SwaggerGenerators, while a change to NSwagStudio.ViewModels.SwaggerGenerators can't break NSwag.Commands.Generation.
- Position
- Below the diagonal: NSwagStudio.ViewModels.SwaggerGenerators uses a module listed above it, which is the healthy direction.
38→10 NSwagStudio.ViewModels.SwaggerGenerators uses NSwag.Commands.Generation.AspNetCore✕
- Connections
- 1 pair of types, where a type in NSwagStudio.ViewModels.SwaggerGenerators uses a type in NSwag.Commands.Generation.AspNetCore.
- The types involved
NSwagStudio.ViewModels.SwaggerGenerators.AspNetCoreToSwaggerGeneratorViewModel→NSwag.Commands.Generation.AspNetCore.AspNetCoreToOpenApiCommand
- Direction
- NSwagStudio.ViewModels.SwaggerGenerators uses NSwag.Commands.Generation.AspNetCore, so a change to NSwag.Commands.Generation.AspNetCore can break NSwagStudio.ViewModels.SwaggerGenerators, while a change to NSwagStudio.ViewModels.SwaggerGenerators can't break NSwag.Commands.Generation.AspNetCore.
- Position
- Below the diagonal: NSwagStudio.ViewModels.SwaggerGenerators uses a module listed above it, which is the healthy direction.
38→33 NSwagStudio.ViewModels.SwaggerGenerators uses NSwag.Commands✕
- Connections
- 2 pairs of types, where a type in NSwagStudio.ViewModels.SwaggerGenerators uses a type in NSwag.Commands.
- The types involved
NSwagStudio.ViewModels.SwaggerGenerators.AspNetCoreToSwaggerGeneratorViewModel→NSwag.Commands.NSwagDocumentNSwagStudio.ViewModels.SwaggerGenerators.AspNetCoreToSwaggerGeneratorViewModel→NSwag.Commands.NewLineBehavior
- Direction
- NSwagStudio.ViewModels.SwaggerGenerators uses NSwag.Commands, so a change to NSwag.Commands can break NSwagStudio.ViewModels.SwaggerGenerators, while a change to NSwagStudio.ViewModels.SwaggerGenerators can't break NSwag.Commands.
- Position
- Below the diagonal: NSwagStudio.ViewModels.SwaggerGenerators uses a module listed above it, which is the healthy direction.
38→37 NSwagStudio.ViewModels.SwaggerGenerators uses NSwagStudio.ViewModels✕
- Connections
- 2 pairs of types, where a type in NSwagStudio.ViewModels.SwaggerGenerators uses a type in NSwagStudio.ViewModels.
- The types involved
NSwagStudio.ViewModels.SwaggerGenerators.AspNetCoreToSwaggerGeneratorViewModel→NSwagStudio.ViewModels.ViewModelBaseNSwagStudio.ViewModels.SwaggerGenerators.SwaggerInputViewModel→NSwagStudio.ViewModels.ViewModelBase
- Direction
- NSwagStudio.ViewModels.SwaggerGenerators uses NSwagStudio.ViewModels, so a change to NSwagStudio.ViewModels can break NSwagStudio.ViewModels.SwaggerGenerators, while a change to NSwagStudio.ViewModels.SwaggerGenerators can't break NSwagStudio.ViewModels.
- Position
- Below the diagonal: NSwagStudio.ViewModels.SwaggerGenerators uses a module listed above it, which is the healthy direction.
39→37 NSwagStudio.Views uses NSwagStudio.ViewModels✕
- Connections
- 3 pairs of types, where a type in NSwagStudio.Views uses a type in NSwagStudio.ViewModels.
- The types involved
NSwagStudio.Views.DocumentView→NSwagStudio.ViewModels.DocumentModelNSwagStudio.Views.DocumentView→NSwagStudio.ViewModels.DocumentViewModelNSwagStudio.Views.MainWindow→NSwagStudio.ViewModels.MainWindowModel
- Direction
- NSwagStudio.Views uses NSwagStudio.ViewModels, so a change to NSwagStudio.ViewModels can break NSwagStudio.Views, while a change to NSwagStudio.Views can't break NSwagStudio.ViewModels.
- Position
- Below the diagonal: NSwagStudio.Views uses a module listed above it, which is the healthy direction.
40→9 NSwagStudio.Views.SwaggerGenerators uses NSwag.Commands.Generation✕
- Connections
- 1 pair of types, where a type in NSwagStudio.Views.SwaggerGenerators uses a type in NSwag.Commands.Generation.
- The types involved
NSwagStudio.Views.SwaggerGenerators.SwaggerInputView→NSwag.Commands.Generation.FromDocumentCommand
- Direction
- NSwagStudio.Views.SwaggerGenerators uses NSwag.Commands.Generation, so a change to NSwag.Commands.Generation can break NSwagStudio.Views.SwaggerGenerators, while a change to NSwagStudio.Views.SwaggerGenerators can't break NSwag.Commands.Generation.
- Position
- Below the diagonal: NSwagStudio.Views.SwaggerGenerators uses a module listed above it, which is the healthy direction.
40→10 NSwagStudio.Views.SwaggerGenerators uses NSwag.Commands.Generation.AspNetCore✕
- Connections
- 1 pair of types, where a type in NSwagStudio.Views.SwaggerGenerators uses a type in NSwag.Commands.Generation.AspNetCore.
- The types involved
NSwagStudio.Views.SwaggerGenerators.AspNetCoreToSwaggerGeneratorView→NSwag.Commands.Generation.AspNetCore.AspNetCoreToOpenApiCommand
- Direction
- NSwagStudio.Views.SwaggerGenerators uses NSwag.Commands.Generation.AspNetCore, so a change to NSwag.Commands.Generation.AspNetCore can break NSwagStudio.Views.SwaggerGenerators, while a change to NSwagStudio.Views.SwaggerGenerators can't break NSwag.Commands.Generation.AspNetCore.
- Position
- Below the diagonal: NSwagStudio.Views.SwaggerGenerators uses a module listed above it, which is the healthy direction.
40→27 NSwagStudio.Views.SwaggerGenerators uses NSwag.Commands.CodeGeneration✕
- Connections
- 1 pair of types, where a type in NSwagStudio.Views.SwaggerGenerators uses a type in NSwag.Commands.CodeGeneration.
- The types involved
NSwagStudio.Views.SwaggerGenerators.JsonSchemaInputView→NSwag.Commands.CodeGeneration.JsonSchemaToOpenApiCommand
- Direction
- NSwagStudio.Views.SwaggerGenerators uses NSwag.Commands.CodeGeneration, so a change to NSwag.Commands.CodeGeneration can break NSwagStudio.Views.SwaggerGenerators, while a change to NSwagStudio.Views.SwaggerGenerators can't break NSwag.Commands.CodeGeneration.
- Position
- Below the diagonal: NSwagStudio.Views.SwaggerGenerators uses a module listed above it, which is the healthy direction.
40→33 NSwagStudio.Views.SwaggerGenerators uses NSwag.Commands✕
- Connections
- 5 pairs of types, where a type in NSwagStudio.Views.SwaggerGenerators uses a type in NSwag.Commands.
- The types involved
NSwagStudio.Views.SwaggerGenerators.AspNetCoreToSwaggerGeneratorView→NSwag.Commands.IOutputCommandNSwagStudio.Views.SwaggerGenerators.AspNetCoreToSwaggerGeneratorView→NSwag.Commands.NSwagDocumentNSwagStudio.Views.SwaggerGenerators.JsonSchemaInputView→NSwag.Commands.IOutputCommandNSwagStudio.Views.SwaggerGenerators.SwaggerInputView→NSwag.Commands.IOutputCommandNSwagStudio.Views.SwaggerGenerators.SwaggerInputView→NSwag.Commands.NSwagDocument
- Direction
- NSwagStudio.Views.SwaggerGenerators uses NSwag.Commands, so a change to NSwag.Commands can break NSwagStudio.Views.SwaggerGenerators, while a change to NSwagStudio.Views.SwaggerGenerators can't break NSwag.Commands.
- Position
- Below the diagonal: NSwagStudio.Views.SwaggerGenerators uses a module listed above it, which is the healthy direction.
40→34 NSwagStudio.Views.SwaggerGenerators uses NSwagStudio✕
- Connections
- 3 pairs of types, where a type in NSwagStudio.Views.SwaggerGenerators uses a type in NSwagStudio.
- The types involved
NSwagStudio.Views.SwaggerGenerators.AspNetCoreToSwaggerGeneratorView→NSwagStudio.ISwaggerGeneratorViewNSwagStudio.Views.SwaggerGenerators.JsonSchemaInputView→NSwagStudio.ISwaggerGeneratorViewNSwagStudio.Views.SwaggerGenerators.SwaggerInputView→NSwagStudio.ISwaggerGeneratorView
- Direction
- NSwagStudio.Views.SwaggerGenerators uses NSwagStudio, so a change to NSwagStudio can break NSwagStudio.Views.SwaggerGenerators, while a change to NSwagStudio.Views.SwaggerGenerators can't break NSwagStudio.
- Position
- Below the diagonal: NSwagStudio.Views.SwaggerGenerators uses a module listed above it, which is the healthy direction.
40→38 NSwagStudio.Views.SwaggerGenerators uses NSwagStudio.ViewModels.SwaggerGenerators✕
- Connections
- 2 pairs of types, where a type in NSwagStudio.Views.SwaggerGenerators uses a type in NSwagStudio.ViewModels.SwaggerGenerators.
- The types involved
NSwagStudio.Views.SwaggerGenerators.AspNetCoreToSwaggerGeneratorView→NSwagStudio.ViewModels.SwaggerGenerators.AspNetCoreToSwaggerGeneratorViewModelNSwagStudio.Views.SwaggerGenerators.SwaggerInputView→NSwagStudio.ViewModels.SwaggerGenerators.SwaggerInputViewModel
- Direction
- NSwagStudio.Views.SwaggerGenerators uses NSwagStudio.ViewModels.SwaggerGenerators, so a change to NSwagStudio.ViewModels.SwaggerGenerators can break NSwagStudio.Views.SwaggerGenerators, while a change to NSwagStudio.Views.SwaggerGenerators can't break NSwagStudio.ViewModels.SwaggerGenerators.
- Position
- Below the diagonal: NSwagStudio.Views.SwaggerGenerators 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 — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 68 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 7 | Medium |
| A07:2025 — Authentication Failures | 2 | High / Critical |
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.); Stop accepting every TLS certificate: remove the always-true validation callback so the platform verifies the chain, hostname and expiry. If one self-signed certificate must be trusted, pin it by public key or thumbprint on the single handler that needs it and reject all others — never process-wide; Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with 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.). | +7.3 pts | Medium | Data Protection |
| Stop accepting every TLS certificate: remove the always-true validation callback so the platform verifies the chain, hostname and expiry. If one self-signed certificate must be trusted, pin it by public key or thumbprint on the single handler that needs it and reject all others — never process-wide. | +6.5 pts | Medium | Cryptographic Hygiene |
| Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. | +2.5 pts | Low | Secret Scanning |
| Resolve the 2 Tests excluded from compilation finding(s) in Test Quality — start with OpenApiQueryParametersOperationParameterProcessorTests.cs, SwaggerQueryParametersOperationParameterProcessorTests.cs. | +1.9 pts | Low | Test Quality |
| Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. | +1.6 pts | Low | Secrets (history) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.6 pts | Low | Static Analysis (SAST) |
| Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). | +1.6 pts | Low | Static Analysis (SAST) |
| Resolve the 1 DisabledAnalyzers finding(s) in Explicit Debt — start with NSwagStudio.csproj. | +1.3 pts | Low | Explicit Debt |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.4 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| src/NSwag.AspNet.WebApi/JsonExceptionFilterAttribute.cs | 4.7 | Mixed | Explicit Debt: FileScopedPragmaDisable |
| src/NSwag.Generation.AspNetCore.Tests/NSwag.Generation.AspNetCore.Tests.csproj | 5.5 | Mixed | Explicit Debt: NoWarnInCsproj |
| src/NSwag.Generation.Tests/NSwag.Generation.Tests.csproj | 5.8 | Mixed | Explicit Debt: NoWarnInCsproj |
| src/NSwag.Core.Tests/HttpLoadingTests.cs | 6.0 | Mixed | Explicit Debt: TodoComment |
| build/_build.csproj | 6.4 | Mixed | Explicit Debt: NoWarnInCsproj |
| src/NSwag.CodeGeneration.CSharp.Tests/NSwag.CodeGeneration.CSharp.Tests.csproj | 6.4 | Mixed | Explicit Debt: NoWarnInCsproj |
| src/NSwag.CodeGeneration.TypeScript.Tests/NSwag.CodeGeneration.TypeScript.Tests.csproj | 6.4 | Mixed | Explicit Debt: NoWarnInCsproj |
| src/NSwag.Core.Tests/NSwag.Core.Tests.csproj | 6.4 | Mixed | Explicit Debt: NoWarnInCsproj |
| src/NSwag.Generation.WebApi.Tests/NSwag.Generation.WebApi.Tests.csproj | 6.4 | Mixed | Explicit Debt: NoWarnInCsproj |
| src/NSwagStudio/NSwagStudio.csproj | 6.4 | Mixed | Explicit Debt: NoWarnInCsproj |
| src/NSwag.Sample.NET100Minimal/NSwag.Sample.NET100Minimal.csproj | 6.4 | Mixed | Explicit Debt: NoWarnInCsproj |
| src/NSwag.Sample.NET110Minimal/NSwag.Sample.NET110Minimal.csproj | 6.4 | Mixed | Explicit Debt: NoWarnInCsproj |
| src/NSwag.Sample.NET80Minimal/NSwag.Sample.NET80Minimal.csproj | 6.4 | Mixed | Explicit Debt: NoWarnInCsproj |
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 67 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 — 67 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, 274 of 291 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).
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (329 contributor(s) across 4316 commit(s) sampled, automation and bot accounts excluded). One of them holds 83% of the history; the other 328 hold 0.1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'src/NSwagStudio.Installer/NSwagStudio.Installer.wixproj' because the file extension '.wixproj' 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. `dotnet build` reported 1 error(s), and the diagnostics it printed were: MSB6006: "wix.exe" exited with code 1.. None of them is a .NET compiler diagnostic, which is the only signal this check reads as "the code does not compile", so the failure is recorded as a build-environment gap rather than a code defect. The usual causes are a project that targets a platform this run cannot build (a Windows-only target framework on a Linux worker) or a build step that shells out to a tool the image does not carry. Solution Shape is scored on structure and is NOT capped. Semantic analysis is independent of this build and covers every project that loaded — but a project whose restore did not complete has no resolved references, so treat its results as absent rather than clean. ★ The reach of that test, stated so this classification can be checked rather than taken on trust: it reads the C# (CS), Visual Basic (BC) and F# (FS) compiler series, and treats SDK, NuGet-restore and MSBuild codes (NETSDK, NU, MSB) as evidence that the build did not run rather than that the code is broken — read the diagnostics named above and judge for yourself. You can widen what we reach: if this build is meant to run off its own platform, without host tooling we do not carry, the diagnostics named above are what stopped it. If it is deliberately platform-bound — a Windows-only desktop product, say — there is nothing to do here: the note records our reach, not a defect in your build.
- 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 — 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D23 Boundary Type-Coupling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (22,234 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"]`.
- D28 Secrets (history) — 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. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `src/NSwag.Sample.NET100/nswag.json`, `src/NSwag.Sample.NET110/nswag.json`, `src/NSwag.Sample.NET80/nswag.json`, `src/NSwag.Sample.NET90/nswag.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan. 2 of 3 declared ecosystem(s) (npm,osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/NSwag.AspNetCore/Extensions/NSwagServiceCollectionExtensions.cs`, `src/NSwag.AspNetCore/HttpRequestExtension.cs`, `src/NSwag.AspNetCore/OAuth2ClientSettings.cs`, `src/NSwag.AspNetCore/ReDocSettings.cs`, `src/NSwag.AspNetCore/SwaggerSettings.cs`, … (+3 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.
- AC6 Visual & motion safety — 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. Visual & motion safety could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentOutOfRangeException: startIndex cannot be larger than length of string. (Parameter 'startIndex').
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via ToolchainServer (src/NSwag.Sample.NET100). the service exited before it opened a port — `ASPNETCORE_URLS=http://127.0.0.1:0 ASPNETCORE_ENVIRONMENT=Development dotnet run --no-build --no-launch-profile --project 'NSwag.Sample.NET100.csproj'`: to run this application. App: artifacts/bin/NSwag.Sample.NET100/debug/NSwag.Sample.NET100 Architecture: x64 Framework: 'Microsoft.NETCore.App', ve…; runtime evidence skipped (launch chosen because src/NSwag.Sample.NET100/NSwag.Sample.NET100.csproj is a Microsoft.NET.Sdk.Web project).
- M4 Documentation accuracy — 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. Documentation accuracy could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: FileNotFoundException: Could not find file 'src/NSwag.Sample.NET100/openapi.json'.
- 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.
- X2 Cancellation propagation — 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. 6 further occurrence(s) are not listed individually; the score already reflects all 46.
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.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- 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.
- 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.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- 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.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- 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.
- 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
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was Build.Publish.get at 17.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with Build.Publish.get (cognitive 17). — Refactoring it lifts Cognitive Complexity from 9.8 to about 10.0/10.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
10 duplicated block group(s) detected. A further 7 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 1 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with Startup.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (24 corresponding lines) finding(s) in Code Duplication — start with JsonExceptionFilterAttribute.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (21 corresponding lines) finding(s) in Code Duplication — start with JsonExceptionFilterAttribute.cs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
76 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
What to do
- Resolve the 4 Off the main sequence finding(s) in Coupling — start with NSwag.Annotations.csproj, NSwag.Core.csproj, NSwag.AspNetCore.Launcher.csproj. — One of this dimension's main actionable groups (4 warning-level).
D6 · Cohesion (LCOM4)
0 of 4 classes have LCOM4 above 3.
D10 · Test Quality
4 skipped, 0 zero-assertion, 4 excluded from compilation in 2 file(s), 3 depending on a live external host, 1 skipped with a live token-identical twin, 169 auto-approving their snapshot in 2 place(s), 1 mock references across 396 tests.
What to do
- Resolve the 2 Tests excluded from compilation finding(s) in Test Quality — start with OpenApiQueryParametersOperationParameterProcessorTests.cs, SwaggerQueryParametersOperationParameterProcessorTests.cs. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 4 Skipped test finding(s) in Test Quality — start with BodyParametersTests.cs (2), RequiredParameterTests.cs, HttpLoadingTests.cs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Depends on a live external host finding(s) in Test Quality — start with HttpLoadingTests.cs (3). — One of this dimension's main actionable groups (3 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). unit: measured (0 flaky).
D13 · Secret Scanning
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D14 · License Compliance
0 of 250 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 45 direct `PackageReference`(s), and 216 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
No churn × complexity hotspots in the window.
D17 · Explicit Debt
58 deducted debt markers + unmeasured dead symbols across 22234 LoC in the .NET projects (1.9/KLoC) → score 6.2. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
What to do
- Resolve the 33 NoWarnInCsproj finding(s) in Explicit Debt — start with NSwag.Generation.AspNetCore.Tests.csproj (4), NSwag.Generation.Tests.csproj (3), _build.csproj (2). — One of this dimension's main actionable groups (33 issue-level).
- Resolve the 1 FileScopedPragmaDisable finding(s) in Explicit Debt — start with JsonExceptionFilterAttribute.cs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 DisabledAnalyzers finding(s) in Explicit Debt — start with NSwagStudio.csproj. — One of this dimension's main actionable groups (1 issue-level).
D18 · Solution Shape
75 projects, 1180 source files, 34357 hand-written lines of code (22189 production / 12168 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 76 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 134 inter-project edges (build NOT measured — `dotnet build` did not complete in the analyzer, so the build half of this dimension is unmeasured rather than failed: the score above rests on structure alone and is not capped. The diagnostics that stopped it are named under Limitations.)
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 4 document(s) read across 30 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D21 · Naming Consistency
0 naming inconsistencies among 14 declarations measured against a convention their peers follow.
D24 · Comment Value
3 of 135 judged comments only repeat the code they sit on (2.2 %). 5 comment(s) in another language or script were not judged.
What to do
- Resolve the 3 redundant comment finding(s) in Comment Value — start with CSharpCompiler.cs, OpenApiToCSharpCommandBase.cs, NSwagDocumentBase.cs. — One of this dimension's main actionable groups (3 recommendation-level).
D26 · Project Cohesion
0 of 38 projects flagged as possibly oversized/incoherent.
D27 · Navigability
82 % of calls cross a namespace and 3 % go through an interface, but 90 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D29 · Static Analysis (SAST)
68 finding(s): 0 critical, 28 high, 36 medium, 4 low. 23 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 11 file(s) — `src/NSwag.AspNetCore/Extensions/NSwagServiceCollectionExtensions.cs` (line 78), `src/NSwag.AspNetCore/HttpRequestExtension.cs` (line 14, lines 14–16), `src/NSwag.AspNetCore/OAuth2ClientSettings.cs` (line 12), `src/NSwag.AspNetCore/ReDocSettings.cs` (line 18, lines 18–20, line 28), `src/NSwag.AspNetCore/SwaggerSettings.cs` (line 16, line 26), … (+6 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.
What to do
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 23 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 (23 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: `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan), so this is not the whole dependency surface and the result is reported at reduced confidence.
D34 · Knowledge Freshness
1 of 15 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/NSwag.AspNetCore.Launcher/Program.cs. Counted over 15 of the 70 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-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 40 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
AC1 · Text alternatives
AC3 · Page structure
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×2) — REDACTED:2, REDACTED:2
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="redoc-container">, so there is no content here to wrap — render the <main> from the component mounted into it. (×2) — REDACTED:2, REDACTED:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AX1 · Captive dependencies
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
AX3 · Project dependency cycles
- The namespaces NSwag.Generation ↔ NSwag.Generation.Processors ↔ NSwag.Generation.Processors.Collections ↔ NSwag.Generation.Processors.Contexts depend on each other. The lightest dependency in the cycle is NSwag.Generation → NSwag.Generation.Processors.Contexts (NSwag.Generation.OpenApiDocumentGeneratorSettings → NSwag.Generation.Processors.Contexts.OperationProcessorContext, 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/NSwag.Generation/OpenApiDocumentGeneratorSettings.cs:15
- The namespaces NSwag.CodeGeneration.CSharp ↔ NSwag.CodeGeneration.CSharp.Models depend on each other. The lightest dependency in the cycle is NSwag.CodeGeneration.CSharp → NSwag.CodeGeneration.CSharp.Models (NSwag.CodeGeneration.CSharp.CSharpClientGenerator → NSwag.CodeGeneration.CSharp.Models.CSharpOperationModel, 5 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/NSwag.CodeGeneration.CSharp/CSharpClientGenerator.cs:11
- The namespaces NSwag.CodeGeneration.TypeScript ↔ NSwag.CodeGeneration.TypeScript.Models depend on each other. The lightest dependency in the cycle is NSwag.CodeGeneration.TypeScript → NSwag.CodeGeneration.TypeScript.Models (NSwag.CodeGeneration.TypeScript.TypeScriptClientGenerator → NSwag.CodeGeneration.TypeScript.Models.TypeScriptOperationModel, 2 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/NSwag.CodeGeneration.TypeScript/TypeScriptClientGenerator.cs:12
- The namespaces NSwag.Commands ↔ NSwag.Commands.CodeGeneration ↔ NSwag.Commands.Generation ↔ NSwag.Commands.Generation.AspNetCore depend on each other. The lightest dependency in the cycle is NSwag.Commands → NSwag.Commands.Generation (NSwag.Commands.OpenApiGeneratorCollection → NSwag.Commands.Generation.FromDocumentCommand, 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/NSwag.Commands/OpenApiGeneratorCollection.cs:3
- The namespaces NSwagStudio.ViewModels ↔ NSwagStudio.ViewModels.CodeGenerators ↔ NSwagStudio.Views.CodeGenerators depend on each other. The lightest dependency in the cycle is NSwagStudio.ViewModels → NSwagStudio.Views.CodeGenerators (NSwagStudio.ViewModels.CodeGeneratorModel → NSwagStudio.Views.CodeGenerators.CodeGeneratorViewBase, 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/NSwagStudio/ViewModels/CodeGeneratorModel.cs:1
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
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.).
GD1 · Unfinished & placeholder code
- A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — src/NSwagStudio/Converters/IsValueToVisibilityConverter.cs:31, src/NSwagStudio/Converters/NumberAdditionConverter.cs:13
What to do
- Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs
- `LoadAsync` 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/NSwag.Commands/NSwagDocumentBase.cs:163
- A test is skipped with reason "TODO" — the behavior it asserts is UNVERIFIED and this skip is likely the only marker of a real bug. It ages invisibly: fix the flakiness or track the bug somewhere that can't be forgotten. — src/NSwag.Core.Tests/HttpLoadingTests.cs:47
- `DocumentView.xaml` wires an event to `OnGenerate`, whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. — src/NSwagStudio/Views/DocumentView.xaml.cs:72
- `Left == double.NaN` is false for every value, including NaN itself: IEEE 754 leaves NaN unordered with everything, so `==` against `double.NaN` never depends on the other operand. Use `double.IsNaN(…)` — the test that was intended, and the branch this guards is dead. — REDACTED:76
- A test is skipped ("The C#11 required keyword does not mark schema properties as required") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. — src/NSwag.CodeGeneration.CSharp.Tests/RequiredParameterTests.cs:62
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×12) — src/NSwag.CodeGeneration.TypeScript/Models/TypeScriptOperationModel.cs:182, src/NSwag.Core/Collections/ObservableDictionary.cs:225, src/NSwag.Core/OpenApiDocument.Serialization.cs:89, …
- A test is skipped ("Wrong in .Net 7") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. (×2) — src/NSwag.Generation.AspNetCore.Tests/Parameters/BodyParametersTests.cs:49, src/NSwag.Generation.AspNetCore.Tests/Parameters/BodyParametersTests.cs:102
What to do
- 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
- 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: 29 of 29 have no README of their own, in their folder or in their family's project (`src/NSwag.CodeGeneration`, `src/NSwagStudio`, `src/NSwag.Annotations`, `src/NSwag.Core`, `src/NSwag.AspNet.Owin` and 24 more).
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
P1 · CI/CD gates
P2 · Observability
- Only 1/21 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 21, 10 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
What to do
- Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
- Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
P3 · Security & performance tooling
- `Directory.Packages.props` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — Directory.Packages.props:7
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
P7 · Outbound HTTP resilience
- Outbound HTTP calls were found with no timeout or retry policy around them. This codebase ships libraries/tools rather than a service it operates, so the failure lands differently: an unbounded call hangs the caller's process — a build step, a CLI run, a UI thread — with no way out.
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.
PF3 · Async & latency hygiene
- 5 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). (×5) — src/NSwag.Commands/Commands/Generation/AspNetCore/AspNetCoreToOpenApiGeneratorCommandEntryPoint.cs:28, src/NSwag.Commands/HostFactoryResolver.cs:265, src/NSwag.Commands/NConsole/CommandLineProcessor.cs:203, …
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
- `ServerCertificateValidationCallback` is assigned a callback that returns `true` unconditionally, so every TLS peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Delete the override and let the platform validate. If a specific self-signed or internally-issued certificate genuinely has to be trusted, pin THAT one — compare the presented certificate's public key or thumbprint against the expected value and return `false` for everything else — and scope it to the single handler that talks to that host rather than to the whole process. If the override exists only to get past a development certificate, gate it on a build configuration or an explicit opt-in setting so it cannot ship. — REDACTED:30
- `https://cdn.jsdelivr.net/npm/redoc/bundles/redoc.standalone.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 2 such include(s) across the repository's markup. — REDACTED:18
What to do
- Stop accepting every TLS certificate: remove the always-true validation callback so the platform verifies the chain, hostname and expiry. If one self-signed certificate must be trusted, pin it by public key or thumbprint on the single handler that needs it and reject all others — never process-wide.
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
X1 · Async correctness
- `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. (×3) — src/NSwagStudio/ViewModels/MainWindowModel.cs:83, REDACTED:58, REDACTED:80
- `StreamReader.ReadToEnd` blocks the thread on I/O while `StreamReader.ReadToEndAsync` exists to wait without one — inside a method that is already `async`, await the twin. — src/NSwag.AspNet.Owin/Middlewares/SwaggerUiIndexMiddleware.cs:29
- 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. (×4) — src/NSwag.Commands/Commands/Generation/AspNetCore/AspNetCoreToOpenApiGeneratorCommandEntryPoint.cs:28, src/NSwag.Commands/NConsole/CommandLineProcessor.cs:203, src/NSwag.Commands/NConsole/CommandLineProcessor.cs:214, …
- `.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/NSwag.Commands/HostFactoryResolver.cs:253
What to do
- async void method: OnLoaded
X12 · Unreachable branch
X13 · Undrained process stream
- `RedirectStandardError` is set here, but `StandardError` is not being read when `StandardOutput` is read to the end — it is never read, read only later, or read only in part. The child blocks as soon as it fills the StandardError pipe (~4 KB, never more than 64 KB), so it never finishes and never exits, and the read or wait above never returns: a `WaitForExit` timeout after a read does not help: the timeout bounds the WAIT, not the read that precedes it. Drain every redirected stream before blocking on the child — read one on a background thread (`BeginErrorReadLine()` with its `DataReceived` handler, or a `Task` running `ReadToEndAsync()` started before the other read and awaited after it) — or stop redirecting the stream you do not consume. — src/NSwag.Commands/NSwagDocument.cs:183
What to do
- Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
- `dlg` is a `OpenFileDialog`, which implements `IDisposable`, and it is created here (line 135). Every use of it in `OpenDocumentAsync` 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 dlg = …;`), which releases it at the end of the scope on every path including a throw. — src/NSwagStudio/ViewModels/MainWindowModel.cs:135
- `dlg` is a `SaveFileDialog`, which implements `IDisposable`, and it is created here (line 246). Every use of it in `SaveAsDocumentAsync` 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 dlg = …;`), which releases it at the end of the scope on every path including a throw. — src/NSwagStudio/ViewModels/MainWindowModel.cs:246
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.
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 8/52 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 — this work can't be stopped early once started. (×35) — src/NSwagStudio/ViewModels/CodeGenerators/SwaggerOutputViewModel.cs:17, src/NSwagStudio/ViewModels/DocumentViewModel.cs:45, src/NSwagStudio/ViewModels/SwaggerGenerators/AspNetCoreToSwaggerGeneratorViewModel.cs:53, …
- No CancellationToken parameter, and the token `context.Request.CallCancelled` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.Request.CallCancelled` on, or take a CancellationToken. — src/NSwag.AspNet.Owin/Middlewares/OpenApiDocumentMiddleware.cs:91
- 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. (×2) — src/NSwag.Commands/Commands/Generation/AspNetCore/Exe.cs:17, src/NSwag.Commands/Commands/Generation/AspNetCore/ProjectMetadata.cs:243
- No CancellationToken parameter, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken. — src/NSwag.AspNetCore/Middlewares/OpenApiDocumentMiddleware.cs:134
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
- The guard on line 195 rejects `name` and line 197 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/NSwag.AspNetCore/SwaggerUiSettings.cs:197
- The guard on line 200 rejects `url` and line 202 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(url)` is true of a value that is NOT null: it is satisfied by an EMPTY `url`, and on that path `url` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/NSwag.AspNetCore/SwaggerUiSettings.cs:202
What to do
- Each finding names the throw and the test in its own condition that is true of a NON-null value. Confirm from the two, then throw the exception that describes what was actually wrong: `ArgumentException` for a value that arrived empty, or the .NET 8 helpers that spell the whole guard in one line and pick the type for you — `ArgumentException.ThrowIfNullOrEmpty(s)` / `ThrowIfNullOrWhiteSpace(s)` for strings, `ArgumentNullException.ThrowIfNull(x)` followed by `ArgumentOutOfRangeException.ThrowIfZero(x.Count)` for a collection. Splitting the two conditions is usually clearer than picking one exception for both: they are different failures and the caller may want to handle them differently.
X24 · Document value interpolated into markup unescaped
- `uriString` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through a `StringBuilder` building markup with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — src/NSwag.AspNetCore/SwaggerUiSettingsBase.cs:85
- `uriString` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this method returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — src/NSwag.AspNetCore/SwaggerUiSettingsBase.cs:116
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- 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. (×4) — src/NSwag.Commands/Commands/Generation/AspNetCore/AspNetCoreToOpenApiCommand.cs:257, src/NSwag.Commands/Commands/Generation/AspNetCore/ProjectMetadata.cs:234, src/NSwag.Commands/Commands/Generation/AspNetCore/ProjectMetadata.cs:337, …
- `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. — src/NSwag.AspNetCore.Launcher/Program.cs:150
What to do
- Swallowed exception (empty catch)
X5 · Nullable reference types
- This method contradicts itself about `returnParameter`: line 280 writes `returnParameter?.`, which says `returnParameter` can be null, but line 262 then dereferences it directly as `returnParameter.ParameterType` 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 `returnParameter` truly cannot be null here, the `?.` is misleading. Settle it one way — test `returnParameter` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/NSwag.Generation/Processors/OperationResponseProcessorBase.cs:262
- 4/10 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
What to do
- 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 `!`.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 56% | Adequate | Acceptable, with room to improve. |
| Architecture | 99% | Exemplary | Strongest area. |
| Maturity | 72% | Strong | Solid. |
| Readiness | 51% | Adequate — gated by P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 38% | Weak — gated by D29, D36, C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 63% | Adequate — gated by AC3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 60% | Adequate | Acceptable, with room to improve. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 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.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, 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 — 44 check(s) not relevant to this codebase
- AC2 Forms & labels — No form control/button found in the parsed markup — AC2 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AC6 Visual & motion safety — Visual & motion safety could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the service exited before it opened a port — `ASPNETCORE_URLS=http://127.0.0.1:0 ASPNETCORE_ENVIRONMENT=Development dotnet run --no-build --no-launch-profile --project 'NSwag.Sample.NET100.csproj'`: to run this application. App: artifacts/bin/NSwag.Sample.NET100/debug/NSwag.Sample.NET100 Architecture: x64 Framework: 'Microsoft.NETCore.App', ve…; runtime evidence skipped (launch chosen because src/NSwag.Sample.NET100/NSwag.Sample.NET100.csproj is a Microsoft.NET.Sdk.Web project) This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- 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.
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- 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) — 8 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 — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Documentation accuracy could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
- P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 75 finding(s)
- NoWarnInCsproj — 6 warning codes suppressed in one element src/NSwag.Generation.AspNetCore.Tests.Web/NSwag.Generation.AspNetCore.Tests.Web.csproj:6
- NoWarnInCsproj build/_build.csproj:7
- NoWarnInCsproj build/_build.csproj:7
- NoWarnInCsproj src/NSwag.CodeGeneration.CSharp.Tests/NSwag.CodeGeneration.CSharp.Tests.csproj:5
- NoWarnInCsproj src/NSwag.CodeGeneration.Tests/NSwag.CodeGeneration.Tests.csproj:4
- NoWarnInCsproj src/NSwag.CodeGeneration.TypeScript.Tests/NSwag.CodeGeneration.TypeScript.Tests.csproj:5
- NoWarnInCsproj src/NSwag.ConsoleCore.Tests/NSwag.ConsoleCore.Tests.csproj:4
- NoWarnInCsproj src/NSwag.Core.Tests/NSwag.Core.Tests.csproj:7
- NoWarnInCsproj src/NSwag.Core.Yaml.Tests/NSwag.Core.Yaml.Tests.csproj:6
- NoWarnInCsproj src/NSwag.Generation.AspNetCore.Tests/NSwag.Generation.AspNetCore.Tests.csproj:4
- NoWarnInCsproj src/NSwag.Generation.Tests/NSwag.Generation.Tests.csproj:7
- NoWarnInCsproj src/NSwag.CodeGeneration.CSharp.Tests/NSwag.CodeGeneration.CSharp.Tests.csproj:5
- NoWarnInCsproj src/NSwag.CodeGeneration.TypeScript.Tests/NSwag.CodeGeneration.TypeScript.Tests.csproj:5
- NoWarnInCsproj src/NSwag.Core.Tests/NSwag.Core.Tests.csproj:7
- NoWarnInCsproj src/NSwag.Generation.AspNetCore.Tests/NSwag.Generation.AspNetCore.Tests.csproj:4
- NoWarnInCsproj src/NSwag.Generation.AspNetCore.Tests/NSwag.Generation.AspNetCore.Tests.csproj:4
- NoWarnInCsproj src/NSwag.Generation.Tests/NSwag.Generation.Tests.csproj:7
- NoWarnInCsproj src/NSwag.Generation.AspNetCore.Tests/NSwag.Generation.AspNetCore.Tests.csproj:4
- NoWarnInCsproj src/NSwag.Generation.Tests/NSwag.Generation.Tests.csproj:7
- NoWarnInCsproj src/NSwag.Generation.WebApi.Tests/NSwag.Generation.WebApi.Tests.csproj:4
- NoWarnInCsproj src/NSwagStudio/NSwagStudio.csproj:15
- NoWarnInCsproj src/NSwag.Generation.WebApi.Tests/NSwag.Generation.WebApi.Tests.csproj:4
- NoWarnInCsproj src/NSwag.Sample.NET100Minimal/NSwag.Sample.NET100Minimal.csproj:4
- NoWarnInCsproj src/NSwag.Sample.NET110Minimal/NSwag.Sample.NET110Minimal.csproj:4
- NoWarnInCsproj src/NSwag.Sample.NET80Minimal/NSwag.Sample.NET80Minimal.csproj:4
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Namespace dependency cycle src/NSwag.Generation/OpenApiDocumentGeneratorSettings.cs:15
- Namespace dependency cycle src/NSwag.CodeGeneration.CSharp/CSharpClientGenerator.cs:11
- Namespace dependency cycle src/NSwag.CodeGeneration.TypeScript/TypeScriptClientGenerator.cs:12
- Namespace dependency cycle src/NSwag.Commands/OpenApiGeneratorCollection.cs:3
- Namespace dependency cycle src/NSwagStudio/ViewModels/CodeGeneratorModel.cs:1
- REDACTED
- REDACTED
- REDACTED
- <html> without a lang REDACTED:2
- <html> without a lang REDACTED:2
- Tests excluded from compilation: src/NSwag.Generation.WebApi.Tests/OperationProcessors/OpenApiQueryParametersOperationParameterProcessorTests.cs src/NSwag.Generation.WebApi.Tests/OperationProcessors/OpenApiQueryParametersOperationParameterProcessorTests.cs:46
- Tests excluded from compilation: src/NSwag.Generation.WebApi.Tests/OperationProcessors/SwaggerQueryParametersOperationParameterProcessorTests.cs src/NSwag.Generation.WebApi.Tests/OperationProcessors/SwaggerQueryParametersOperationParameterProcessorTests.cs:46
- REDACTED
- FileScopedPragmaDisable src/NSwag.AspNet.WebApi/JsonExceptionFilterAttribute.cs:86
- DisabledAnalyzers src/NSwagStudio/NSwagStudio.csproj:16
- REDACTED
- REDACTED
- REDACTED
- TLS certificate validation disabled REDACTED:30
Serious — 160 finding(s)
- Async method without CancellationToken: GenerateClientAsync src/NSwagStudio/ViewModels/CodeGenerators/SwaggerOutputViewModel.cs:17
- Async method without CancellationToken: GenerateAsync src/NSwagStudio/ViewModels/DocumentViewModel.cs:45
- Async method without CancellationToken: GenerateSwaggerAsync src/NSwagStudio/ViewModels/SwaggerGenerators/AspNetCoreToSwaggerGeneratorViewModel.cs:53
- Async method without CancellationToken: LoadSwaggerUrlAsync src/NSwagStudio/ViewModels/SwaggerGenerators/SwaggerInputViewModel.cs:21
- Async method without CancellationToken: GenerateSwaggerAsync src/NSwagStudio/ViewModels/SwaggerGenerators/SwaggerInputViewModel.cs:39
- Async method without CancellationToken: GenerateSwaggerAsync src/NSwagStudio/Views/SwaggerGenerators/JsonSchemaInputView.xaml.cs:22
- Async method without CancellationToken: GenerateDocumentAsync src/NSwag.AspNet.Owin/Middlewares/OpenApiDocumentMiddleware.cs:91
- Async method without CancellationToken: RunAsync src/NSwag.Commands/Commands/CodeGeneration/JsonSchemaToCSharpCommand.cs:261
- Async method without CancellationToken: RunAsync src/NSwag.Commands/Commands/CodeGeneration/JsonSchemaToOpenApiCommand.cs:18
- Async method without CancellationToken: RunAsync src/NSwag.Commands/Commands/CodeGeneration/JsonSchemaToOpenApiCommand.cs:23
- Async method without CancellationToken: RunAsync src/NSwag.Commands/Commands/CodeGeneration/JsonSchemaToTypeScriptCommand.cs:22
- Async method without CancellationToken: RunAsync src/NSwag.Commands/Commands/CodeGeneration/OpenApiToCSharpClientCommand.cs:255
- Async method without CancellationToken: RunAsync src/NSwag.Commands/Commands/CodeGeneration/OpenApiToCSharpClientCommand.cs:266
- Async method without CancellationToken: RunAsync src/NSwag.Commands/Commands/CodeGeneration/OpenApiToCSharpControllerCommand.cs:80
- Async method without CancellationToken: RunAsync src/NSwag.Commands/Commands/CodeGeneration/OpenApiToCSharpControllerCommand.cs:87
- Async method without CancellationToken: RunAsync src/NSwag.Commands/Commands/CodeGeneration/OpenApiToTypeScriptClientCommand.cs:409
- Async method without CancellationToken: RunAsync src/NSwag.Commands/Commands/CodeGeneration/OpenApiToTypeScriptClientCommand.cs:416
- Async method without CancellationToken: RunAsync src/NSwag.Commands/Commands/Document/ExecuteDocumentCommand.cs:24
- Async method without CancellationToken: ExecuteDocumentAsync src/NSwag.Commands/Commands/Document/ExecuteDocumentCommand.cs:56
- Async method without CancellationToken: RunAsync src/NSwag.Commands/Commands/Generation/AspNetCore/AspNetCoreToOpenApiCommand.cs:62
- Async method without CancellationToken: GenerateDocumentAsync src/NSwag.Commands/Commands/Generation/AspNetCore/AspNetCoreToOpenApiCommand.cs:233
- Async method without CancellationToken: GenerateDocumentWithDocumentProviderAsync src/NSwag.Commands/Commands/Generation/AspNetCore/AspNetCoreToOpenApiCommand.cs:239
- Async method without CancellationToken: GetProjectMetadata src/NSwag.Commands/Commands/Generation/AspNetCore/ProjectMetadata.cs:72
- Async method without CancellationToken: RunAsync REDACTED:50
- Async method without CancellationToken: RunAsync REDACTED:58
- 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
- BarePragmaDisable src/NSwag.CodeGeneration.CSharp.Tests/OptionalParameterTests.cs:32
- BarePragmaDisable src/NSwag.Generation.AspNetCore.Tests.Web/Controllers/Parameters/DefaultParametersController.cs:21
- BarePragmaDisable REDACTED:20
- BarePragmaDisable REDACTED:20
- BarePragmaDisable REDACTED:20
- BarePragmaDisable REDACTED:20
- BarePragmaDisable src/NSwag.CodeGeneration.CSharp.Tests/OptionalParameterTests.cs:44
- BarePragmaDisable src/NSwag.Generation.AspNetCore.Tests/AspNetCoreToSwaggerGenerationTests.cs:910
- BarePragmaDisable src/NSwag.Generation.AspNetCore.Tests/Processors/OperationResponseProcessorTest.cs:151
- TodoComment src/NSwag.CodeGeneration.CSharp.Tests/FormParameterTests.cs:129
- TodoComment src/NSwag.CodeGeneration.CSharp.Tests/ResponseTests.cs:518
- TodoComment src/NSwag.ConsoleCore/CoreConsoleHost.cs:5
- TodoComment src/NSwag.Core.Tests/HttpLoadingTests.cs:46
- TodoComment src/NSwag.Generation.AspNetCore.Tests.Web/Controllers/Parameters/ComplexQueryParametersController.cs:23
- TodoComment src/NSwagStudio/Controls/TabContent.cs:9
- TodoComment src/NSwagStudio/Views/DocumentView.xaml.cs:74
- TodoComment src/NSwagStudio/Views/SwaggerGenerators/JsonSchemaInputView.xaml.cs:35
- Sync-over-async blocking
- Sync-over-async blocking src/NSwag.Commands/Commands/Generation/AspNetCore/AspNetCoreToOpenApiGeneratorCommandEntryPoint.cs:28
- Sync-over-async blocking src/NSwag.Commands/HostFactoryResolver.cs:265
- Sync-over-async blocking src/NSwag.Commands/NConsole/CommandLineProcessor.cs:203
- Sync-over-async blocking src/NSwag.Commands/NConsole/CommandLineProcessor.cs:214
- Sync-over-async blocking src/NSwag.Commands/NSwagCommandProcessor.cs:32
- Skipped test: When_setting_is_enabled_properties_with_required_keyword_should_generate_with_required_keyword src/NSwag.CodeGeneration.CSharp.Tests/RequiredParameterTests.cs:62
- Skipped test: When_primitive_body_parameter_has_default_value_then_it_is_required_before_net7 src/NSwag.Generation.AspNetCore.Tests/Parameters/BodyParametersTests.cs:49
- Skipped test: When_complex_body_parameter_has_default_value_then_it_is_required_before_net7 src/NSwag.Generation.AspNetCore.Tests/Parameters/BodyParametersTests.cs:102
- Skipped test: When_OpenApi_is_loaded_from_url_schematype_is_OpenApi3 src/NSwag.Core.Tests/HttpLoadingTests.cs:47
- Off the main sequence: NSwag.Annotations(net462) src/NSwag.Annotations/NSwag.Annotations.csproj:1
- Off the main sequence: NSwag.Core(net462) src/NSwag.Core/NSwag.Core.csproj:1
- Off the main sequence: NSwag.AspNetCore.Launcher(net8.0) src/NSwag.AspNetCore.Launcher/NSwag.AspNetCore.Launcher.csproj:1
- Off the main sequence: NSwag.AspNetCore.Launcher.x86 src/NSwag.AspNetCore.Launcher.x86/NSwag.AspNetCore.Launcher.x86.csproj:1
- Sync-over-async (deadlock risk) src/NSwag.Commands/Commands/Generation/AspNetCore/AspNetCoreToOpenApiGeneratorCommandEntryPoint.cs:28
- Sync-over-async (deadlock risk) src/NSwag.Commands/NConsole/CommandLineProcessor.cs:203
- Sync-over-async (deadlock risk) src/NSwag.Commands/NConsole/CommandLineProcessor.cs:214
- Sync-over-async (deadlock risk) src/NSwag.Commands/NSwagCommandProcessor.cs:32
- Swallowed exception (empty catch) src/NSwag.Commands/Commands/Generation/AspNetCore/AspNetCoreToOpenApiCommand.cs:257
- Swallowed exception (empty catch) src/NSwag.Commands/Commands/Generation/AspNetCore/ProjectMetadata.cs:234
- Swallowed exception (empty catch) src/NSwag.Commands/Commands/Generation/AspNetCore/ProjectMetadata.cs:337
- Swallowed exception (empty catch) src/NSwag.Generation.AspNetCore/AspNetCoreOpenApiDocumentGenerator.cs:165
- Depends on a live external host: When_Swagger_is_loaded_from_url_then_it_works src/NSwag.Core.Tests/HttpLoadingTests.cs:7
- Depends on a live external host: When_Swagger_is_loaded_from_url_schematype_is_Swagger2 src/NSwag.Core.Tests/HttpLoadingTests.cs:20
- Depends on a live external host: When_openapi_is_loaded_without_scopes_it_should_deserialize src/NSwag.Core.Tests/HttpLoadingTests.cs:33
- async void method: OnLoaded src/NSwagStudio/ViewModels/MainWindowModel.cs:83
- async void method: CheckForApplicationUpdate REDACTED:58
- async void method: OnClosing REDACTED:80
- Page without a main landmark REDACTED:2
- Page without a main landmark REDACTED:2
- Snapshot tests auto-approve: src/NSwag.CodeGeneration.Tests/VerifyHelper.cs src/NSwag.CodeGeneration.Tests/VerifyHelper.cs:44
- Snapshot tests auto-approve: src/NSwag.ConsoleCore.Tests/GenerateSampleSpecificationTests.cs src/NSwag.ConsoleCore.Tests/GenerateSampleSpecificationTests.cs:119
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Unfinished stub — throws NotImplementedException src/NSwagStudio/Converters/IsValueToVisibilityConverter.cs:31
- Unfinished stub — throws NotImplementedException src/NSwagStudio/Converters/NumberAdditionConverter.cs:13
- Disposable created and abandoned in the method that made it src/NSwagStudio/ViewModels/MainWindowModel.cs:135
- Disposable created and abandoned in the method that made it src/NSwagStudio/ViewModels/MainWindowModel.cs:246
- Argument guard throws the exception its own condition disproves src/NSwag.AspNetCore/SwaggerUiSettings.cs:197
- Argument guard throws the exception its own condition disproves src/NSwag.AspNetCore/SwaggerUiSettings.cs:202
- Untrusted text written into markup unescaped src/NSwag.AspNetCore/SwaggerUiSettingsBase.cs:85
- Untrusted text written into markup unescaped src/NSwag.AspNetCore/SwaggerUiSettingsBase.cs:116
- No data-protection/encryption
- Build.Publish.get (cognitive 17) build/Build.Publish.cs:28
- REDACTED
- REDACTED
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/NSwag.Sample.NET100/Startup.cs:35
- Edited copy of a member (24 corresponding lines) src/NSwag.AspNet.WebApi/JsonExceptionFilterAttribute.cs:80
- Edited copy of a member (21 corresponding lines) src/NSwag.AspNet.WebApi/JsonExceptionFilterAttribute.cs:57
- Edited copy of a member (19 corresponding lines) src/NSwag.AspNet.Owin/SwaggerExtensions.cs:121
- Edited copy of a member (4 corresponding lines) src/NSwag.Core.Yaml/OpenApiYamlDocument.cs:146
- Duplicated block (23 lines × 3) src/NSwag.Sample.NET100/Startup.cs:36
- Duplicated block (20 lines × 2) src/NSwag.AspNet.WebApi/JsonExceptionFilterAttribute.cs:22
- Duplicated block (17–18 lines × 4) src/NSwag.Sample.NET100/Startup.cs:35
- Duplicated block (16 lines × 2) src/NSwag.AspNet.WebApi/JsonExceptionFilterAttribute.cs:107
- Duplicated block (14 lines × 2) src/NSwag.AspNet.WebApi/JsonExceptionFilterAttribute.cs:90
- Duplicated block (8 lines × 2) src/NSwag.AspNet.Owin/SwaggerExtensions.cs:123
- Duplicated block (6 lines × 4) src/NSwag.Sample.NET100/Program.cs:10
- Duplicated block (37 lines × 3) REDACTED:15
- Duplicated block (42 lines × 2) REDACTED:33
- Duplicated block (16 lines × 4) src/NSwag.Sample.NET100/Startup.cs:17
- Fake-async — async method never awaits src/NSwag.Commands/NSwagDocumentBase.cs:163
- Skipped test marks a known-real bug src/NSwag.Core.Tests/HttpLoadingTests.cs:47
- Markup wires an event to an empty handler src/NSwagStudio/Views/DocumentView.xaml.cs:72
- Comparison is always false — nothing compares equal to NaN REDACTED:76
- Outbound HTTP without resilience
- Third-party script without Subresource Integrity REDACTED:18
- Blocking `StreamReader.ReadToEnd` inside an `async` method src/NSwag.AspNet.Owin/Middlewares/SwaggerUiIndexMiddleware.cs:29
- Sync-over-async (deadlock risk) through `.Wait(…)` src/NSwag.Commands/HostFactoryResolver.cs:253
- Redirected process stream is never drained (deadlock) src/NSwag.Commands/NSwagDocument.cs:183
- Swallowed exception (caught, then discarded) src/NSwag.AspNetCore.Launcher/Program.cs:150
- Symbol treated as nullable, then dereferenced unguarded src/NSwag.Generation/Processors/OperationResponseProcessorBase.cs:262
Minor — 40 finding(s)
- Commented-out code src/NSwag.CodeGeneration.TypeScript/Models/TypeScriptOperationModel.cs:182
- Commented-out code src/NSwag.Core/Collections/ObservableDictionary.cs:225
- Commented-out code src/NSwag.Core/OpenApiDocument.Serialization.cs:89
- Commented-out code src/NSwag.Core/OpenApiDocument.Serialization.cs:92
- Commented-out code src/NSwag.Sample.NET100/Startup.cs:51
- Commented-out code src/NSwag.Sample.NET100/Startup.cs:54
- Commented-out code src/NSwag.Sample.NET110/Startup.cs:51
- Commented-out code src/NSwag.Sample.NET110/Startup.cs:54
- Commented-out code src/NSwag.Sample.NET80/Startup.cs:57
- Commented-out code src/NSwag.Sample.NET80/Startup.cs:60
- Commented-out code src/NSwag.Sample.NET90/Startup.cs:51
- Commented-out code src/NSwag.Sample.NET90/Startup.cs:54
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- redundant comment src/NSwag.CodeGeneration.CSharp.Tests/CSharpCompiler.cs:44
- redundant comment src/NSwag.Commands/Commands/CodeGeneration/OpenApiToCSharpCommandBase.cs:147
- redundant comment src/NSwag.Commands/NSwagDocumentBase.cs:576
- Disabled test src/NSwag.CodeGeneration.CSharp.Tests/RequiredParameterTests.cs:62
- Disabled test src/NSwag.Generation.AspNetCore.Tests/Parameters/BodyParametersTests.cs:49
- Disabled test src/NSwag.Generation.AspNetCore.Tests/Parameters/BodyParametersTests.cs:102
- Duplicated predicate src/NSwag.AspNet.WebApi/JsonExceptionFilterAttribute.cs:58
- Duplicated predicate src/NSwag.AspNet.WebApi/JsonExceptionFilterAttribute.cs:96
- Silent fallback default in catch src/NSwag.Commands/HostFactoryResolver.cs:65
- Silent fallback default in catch src/NSwag.Generation.AspNetCore/AspNetCoreOpenApiDocumentGenerator.cs:69
- No ADRs found
- Orphaned files with no living knowledge
- Orphaned file src/NSwag.AspNetCore.Launcher/Program.cs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Logging is not universal
- No dependency-update automation Directory.Packages.props:7
- No release approval gate
- Not all async methods take a CancellationToken
- Nullable reference types not enabled everywhere
Minor — 16 finding(s)
- doc comments repeat the names src/NSwag.Annotations/OpenApiExtensionDataAttribute.cs:20
- doc comments repeat the names src/NSwag.AspNet.Owin/Middlewares/OpenApiDocumentMiddleware.cs:28
- doc comments repeat the names src/NSwag.AspNetCore/ApiverseUiSettings.cs:13
- doc comments repeat the names src/NSwag.CodeGeneration/ClientGeneratorBase.cs:17
- doc comments repeat the names src/NSwag.CodeGeneration.CSharp/CSharpClientGenerator.cs:22
- doc comments repeat the names src/NSwag.CodeGeneration.TypeScript/Models/TypeScriptClientTemplateModel.cs:13
- doc comments repeat the names src/NSwag.Commands/CodeGeneratorCollection.cs:23
- doc comments repeat the names src/NSwag.Core/Collections/ObservableDictionary.cs:38
- doc comments repeat the names src/NSwag.Core.Yaml/OpenApiYamlDocument.cs:25
- doc comments repeat the names src/NSwag.Generation/IOpenApiDocumentGenerator.cs:15
- doc comments repeat the names src/NSwag.Generation.AspNetCore/AspNetCoreOpenApiDocumentGenerator.cs:36
- doc comments repeat the names src/NSwag.Generation.AspNetCore.Tests.Web/Controllers/XmlDocsController.cs:16
- doc comments repeat the names src/NSwag.Generation.Tests/Processors/OperationSummaryAndDescriptionProcessorTests.cs:25
- doc comments repeat the names src/NSwag.Generation.WebApi/Processors/OperationParameterProcessor.cs:26
- doc comments repeat the names src/NSwagStudio/ISwaggerGeneratorView.cs:16
- Mock framework: Moq
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-06a0283e858e42de98bcb76d24f263d1/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-06a0283e858e42de98bcb76d24f263d1/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude src/NSwag.AspNet.Owin/SwaggerUi --exclude src/NSwag.AspNetCore/SwaggerUi . | 68 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan | 0 | — |
| 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 8 file(s) — `src/NSwag.AspNetCore/Extensions/NSwagServiceCollectionExtensions.cs`, `src/NSwag.AspNetCore/HttpRequestExtension.cs`, `src/NSwag.AspNetCore/OAuth2ClientSettings.cs`, `src/NSwag.AspNetCore/ReDocSettings.cs`, `src/NSwag.AspNetCore/SwaggerSettings.cs`, … (+3 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 |
Appendix C — Personal-data map
Name — 8 field(s)
- Person.FirstName REDACTED:11
- Person.LastName REDACTED:15
- Person.FirstName REDACTED:11
- Person.LastName REDACTED:15
- Person.FirstName REDACTED:11
- Person.LastName REDACTED:15
- Person.FirstName REDACTED:11
- Person.LastName REDACTED:15
Email — 1 field(s)
- OpenApiContact.Email src/NSwag.Core/OpenApiContact.cs:27