revive vs SwiftLint
revive
revive.runSwiftLint
realm.github.ioSide by side
| Figure | revive | SwiftLint |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | — | Yes |
| Self-hosted | Yes | — |
| Plans published | 0 | 1 |
| Spec score · Linters | 6.8 (#32) | 8.0 (#11) |
| CI integrations | The documentation describes a GitHub Action with annotation support and use through golangci-lint and MegaLinter. | SwiftLint documents a Fastlane action and a Docker image, and says it is embedded in MegaLinter. |
| Configuration | Rules can be enabled, disabled, and configured in a TOML file, including per-rule severity and exit codes. | File inclusions and exclusions can be configured in a `.swiftlint.yml` configuration file. |
| License | The repository lists the project license as MIT. | The GitHub repository identifies SwiftLint as MIT licensed. |
| Purpose | Revive is a fast, configurable, extensible linter for Go and a drop-in replacement for golint. | 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.