Top 20 NuGet Packages depending on Microsoft.OpenApi

Total dependencies: 68

Middleware to expose Swagger JSON endpoints from APIs built on ASP.NET Core
Some additional useful filters for Swashbuckle.AspNetCore. This package replaces Swashbuckle.AspNetCore.Examples.
Provide http channel implementation for NetRpc.
This package helps render Open API document and Swagger UI through Azure Functions endpoints.
OpenAPI.NET Readers for JSON and YAML documents
Carter is framework that is a thin layer of extension methods and functionality over ASP.NET Core allowing code to be more explicit and most importantly more enjoyable.
Swagger helpers.
Emeraude Framework is a powerful library providing abstractions, builders and ready to use ASP.NET Core structure for creating SEO friendly web applications based on SSR Vue.js and mobile applications based on Xamarin Forms.
An easy to use web services library built on top of Asp.Net Core 3.1
Core components for Swagger/OpenAPI-driven integration testing APIs built on ASP.NET Core
This package helps render OpenAPI document and Swagger UI of Azure Functions endpoints through the in-process worker.
OpenRPC document generator from JSON-RPC API
A convention-based dotnet plugin that will automatically expose all your declared smoke tests behind a /smoke resource in your API.
QAToolKit Swagger library, that parses Swagger files and produces a common list of HTTP requests.
Generate C# SDKs directly from OpenAPI 3 specifications using the Roslyn compiler.
INTERNAL USE ONLY: Common library used by neonKUBE related projects.
Barber is cli-tool for generating files based on mustache templates. In addition it can read and process OpenAPI 3 specifications and generate code based on templates.
AuthorizationSecurity is based on endpoint authorization framework.You only write database code and mark endpoint can complete the authorization.
This project is a middleware allowing to build automatically a complete RESTful API that will pick its data via CRUD operations in a database. All database requests and Swagger documentation are generated based upon a description stored in database or json file.
Kanyon.Kubernetes provides all of the objects exposed by the standard Kubernetes API as Manifest objects that can be included in a Kanyon manifest.