swagger-api/swagger-ui

This system is a documentation and API testing interface that renders interactive API specifications (Swagger 2.0, OpenAPI 3.0/3.1/3.2) into a web-based UI. It provides a plugin-based architecture for rendering schema definitions, handling authentication flows (OAuth2, OIDC, mTLS), and generating request snippets. The application supports both standalone web deployment and React component integration, featuring a modular core that manages state, error handling, and dynamic configuration.

This period was defined by a comprehensive architectural overhaul, introducing a modular plugin-based core and modern React patterns. The project simultaneously upgraded to OpenAPI 3.x support and migrated the styling system to SCSS with dark mode capabilities.

27 changes

This period focused on expanding the project's reach by introducing a React component wrapper and Docker configuration support, while simultaneously establishing a robust end-to-end and unit testing infrastructure using Cypress, Selenium, and Jest. The work also included modularizing the Webpack build system and enforcing stricter import and security standards.

34 changes

This period focused on implementing comprehensive support for OpenAPI 3.1.0 and JSON Schema 2020-12, introducing new plugins and UI components to render these specifications. The work included building interactive schema rendering, authentication forms for mTLS and HTTP Basic/Bearer, and a modular preset architecture to manage version-specific logic. Extensive testing was added to verify accessibility, security, and functional correctness across these new features.

31 changes

This period focused on adding support for OpenAPI 3.2.0 and consolidating syntax highlighting and JSON Schema 5 rendering into dedicated plugins. The team also significantly improved the application's stability by refactoring the configuration system to enforce strict type casting and adding comprehensive end-to-end and unit tests for the new features.

12 changes

swagger-api/swagger-ui was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.