Open Source Mobile Operating Systems Linters

No configuration, which means no decisions to make, nothing to argue about and no special files to manage. While this might sound extreme, keep in mind that ktlint tries to capture (reflect) official code style from kotlinlang.org and Android Kotlin Style Guide (+ we respect your .editorconfig and support additional ruleset|s). Built-in formatter. So that you wouldn't have to fix all style violations by hand. Customizable output. plain (+ plain?group_by_file), JSON, HTML and check style reporters are available out-of-the-box. It's also easy to create your own. A single executable jar with all dependencies included. ktlint is a single binary with both linter & formatter included. All you need is to drop it in (no need to get overwhelmed while choosing among dozens of code style options).

Zally, a minimalistic, simple-to-use API linter. 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.