Zally is a quality assurance tool. It's a linter for OpenAPI specifications, which:
- Increases the quality of APIs
- Checks compliance
- Delivers early feedback for API designers
- Ensures the same look-and-feel of APIs
- Supports API-First approach
- Provides best practices and advices
Its standard configuration will check your APIs against the rules defined in Zalando's RESTful Guidelines, but anyone can use it out-of-the-box.
Zally's easy-to-use CLI uses the server in the background so that you can check your API on the spot. It also features an intuitive Web UI that shows implemented rules and lints external files and (with its online editor) API definitions.
- Support for OpenAPI 3 and (Swagger) OpenAPI 2 specifications
- RESTful API, CLI and Web interface
- Rich Check configuration
- Ignore functionality (
x-zally-ignore
extension) - Java/Kotlin API for new Checks + helper functions
Trying out Zally is easy. You can build and run the whole Zally stack (web-ui, server and database) by executing:
./build-and-run.sh
Web UI is accessible on http://localhost:8080
; Zally server on http://localhost:8000
Please consult the following documents for more information:
- Zally Concepts
- How to operate Zally tools
- How to use Zally
- How to develop new Rules
- Building Under Windows Subsystem for Linux
Zally welcomes contributions from the open source community. To get started, take a look at our contributing guidelines. Then check our Project Board and Issues Tracker for ideas.
For Zally version 1.5, we're focusing on:
- Improve extansability of Zally
- Plugin mechanism for Rules (Sets)
- Utilities and helper functions for Check development
- Improve quality by introducing a better testing approach for integration tests
- Make the usage of Zally easier by roviding high-quality documentation for
- End users
- Check developers
- Operators and administrators
If you have ideas for these items, please let us know.
Feel free to join our Gitter room or contact one of the maintainers directly.
MIT license with an exception. See license file.