Credo vs SwiftLint
Credo
credo.hexdocs.pmSwiftLint
realm.github.ioSide by side
| Figure | Credo | SwiftLint |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | — | Yes |
| Plans published | 1 | 1 |
| Spec score · Linters | 7.8 (#15) | 8.0 (#11) |
| Configuration | Credo uses a `.credo.exs` configuration file that can be placed in the project root or its `config/` folder. | File inclusions and exclusions can be configured in a `.swiftlint.yml` configuration file. |
| Integrations | The maker lists integrations for IntelliJ, Atom, VS Code, Emacs, Kakoune, Neovim, and Codacy. | Documented integrations include Swift Package Manager and Xcode plugins, pre-commit, Fastlane, Docker, Visual Studio Code, and MegaLinter. |
| License | Credo is released under the MIT License. | The GitHub repository identifies SwiftLint as MIT licensed. |
| Output | Credo can output command results as JSON. | The command line supports linting, analysis, baselines, rule listings, and multiple reporters. |
| Purpose | Credo is a static code analysis tool for Elixir focused on code consistency and teaching. | SwiftLint enforces Swift style and conventions based on rules generally accepted by the Swift community. |
Plans
In their own words
SwiftLint
SwiftLint is a free, MIT-licensed tool that checks Swift source against style rules and conventions accepted by the Swift community. It includes more than 200 built-in rules, with opt-in rules disabled by default. A project can set active rules, included and excluded paths, and rule settings in a `.swiftlint.yml` file. SwiftLint can automatically correct some violations, overwriting affected files, and its command line supports linting, analysis, baselines, rule listings, and multiple reporters. Documented integrations include Xcode and Swift Package Manager plugins, pre-commit, Fastlane, Docker, Visual Studio Code, and MegaLinter. Installation choices include package managers, prebuilt packages, and source builds. Releases include macOS, Windows, and Linux binaries. SwiftLint is intended for valid, compilable source, and non-compiling code may produce unexpected results, especially when autocorrecting. Analyzer rules are considerably slower than lint rules. The project is maintained by volunteers, and the maintainers describe it as non-commercial.