Reek
6.1#17 in lintersFree planFree planLinux
VisitReek vs SwiftLint
What both publish
| Fact | Reek | SwiftLint |
|---|---|---|
| Configuration | Reek supports a `.reek.yml` configuration file and permits smell warnings to be suppressed with source code comments. | File inclusions and exclusions can be configured in a `.swiftlint.yml` configuration file. |
| Integrations | The README lists editor integrations for Vim, TextMate, Atom, SublimeLinter, VS Code, and Emacs. | Documented integrations include Swift Package Manager and Xcode plugins, pre-commit, Fastlane, Docker, Visual Studio Code, and MegaLinter. |
| License | GitHub identifies the repository license as MIT. | The GitHub repository identifies SwiftLint as MIT licensed. |
| Output | Reek supports plain text, HTML, YAML, JSON, XML, and GitHub output formats. | The command line supports linting, analysis, baselines, rule listings, and multiple reporters. |
| Purpose | Reek examines Ruby classes, modules, and methods and reports code smells. | SwiftLint enforces Swift style and conventions based on rules generally accepted by the Swift community. |
Reek plans
- ReekFree
SwiftLint plans
- SwiftLintFree
Pick Reek if…
It suits Ruby developers and teams that want configurable code-smell reports in editors, Rails projects, or CI workflows. Its formats and integrations support varied development setups.
Pick SwiftLint if…
SwiftLint suits developers and teams who want to check Swift code against configurable style rules within their editor, build, or CI workflows. It is intended for valid, compilable Swift source.