Linters · 5 tools
Top 5 Kotlin code smell and style tools for Android and backend teams
detekt, SonarLint and SonarQube are the first three tools on this shortlist for detecting code smells and enforcing style in Kotlin and Android codebases. It is written for Kotlin developers on Android and backend teams: detekt is a Kotlin-native analyzer, while the others are multi-language tools that sit in the editor or in pull request workflows.
| # | Tool | Best for | Key feature | Platforms / deployment | Pricing | More |
|---|---|---|---|---|---|---|
| 1 | detektdetekt | Kotlin-native code smell analysis in Gradle projects | Plugins for Gradle, Maven and Bazel, plus a first-party Gradle plugin | Gradle, Maven and Bazel; Android, JVM, JS, Native and Multiplatform projects | See vendor pricing page | Introduction |
| 2 | SonarLintSonar | Real-time feedback inside the IDE | Detects bugs, code smells, vulnerabilities and security hotspots | Visual Studio, VS Code, Eclipse, JetBrains IDEs; cloud IDEs such as GitHub Codespaces and GitPod | See vendor pricing page | Introduction |
| 3 | SonarQubeSonar | Teams enforcing quality gates on pull requests | Analyzes branches and pull requests for bugs, maintainability issues and technical debt across 45+ languages | Managed cloud or self-hosted server; Git platform and editor integrations | See vendor pricing page | Introduction |
| 4 | CodacyCodacy | Organizations applying one coding standard across projects | Coding standards defined once and applied as a global policy across all projects | Not stated on official pages | See vendor pricing page | Introduction |
| 5 | DeepSourceDeepSource | Pull request analysis that surfaces only new issues | Reviews every pull request with deterministic rules plus an AI review agent | Not stated on official pages | See vendor pricing page | Introduction |
1 detekt
By detekt
detekt is an open-source static code analyzer for Kotlin that detects code smells and is configurable and extensible.
Why it is here: It is the only tool here built specifically for Kotlin, with documented support for Android, JVM, JS, Native and Multiplatform projects.
- Best for
- Kotlin-native code smell analysis in Gradle projects
- Key features
- Plugins for Gradle, Maven and Bazel, plus a first-party Gradle plugin
- Baselines let legacy projects suppress existing issues while blocking new ones
- Custom rules and rule sets for tracking anti-patterns
- Wrapper over ktlint as a rule set for style checks
- Reports in HTML, Markdown, SARIF and Checkstyle (XML) formats
- Limits
- It is documented as a Kotlin analyzer, so teams that need one tool across several languages should check the vendor documentation for other options. Security scanning is not described in the facts we used.
- Platforms / deployment
- Gradle, Maven and Bazel; Android, JVM, JS, Native and Multiplatform projects
- Pricing
- See vendor pricing page (not quoted here; facts checked 21 November 2026, Asia/Dhaka)
Official website (detekt.dev) · Read our introduction to detekt
2 SonarLint
By Sonar
SonarLint, now called SonarQube for IDE, is an editor extension that gives real-time feedback on bugs and security vulnerabilities with guidance and quick fixes as you code.
Why it is here: It follows detekt because it brings code smell detection into the editor as you write, which suits Android developers working in JetBrains IDEs, but it is multi-language rather than Kotlin-specific.
- Best for
- Real-time feedback inside the IDE
- Key features
- Detects bugs, code smells, vulnerabilities and security hotspots
- Supports Visual Studio, VS Code, Eclipse and the JetBrains IDE family
- A focus-on-new-code setting filters issues to the current development cycle
- Connected Mode syncs rules and quality gates from SonarQube Server or SonarQube Cloud
- Explanations, risks, rule details and code examples in the editor
- Limits
- The pages we used do not list Kotlin among the supported languages, so Kotlin rule coverage should be confirmed in the vendor documentation. Using the same rules as central projects requires Connected Mode.
- Platforms / deployment
- Visual Studio, VS Code, Eclipse, JetBrains IDEs; cloud IDEs such as GitHub Codespaces and GitPod
- Pricing
- See vendor pricing page (not quoted here; facts checked 21 November 2026, Asia/Dhaka)
Official website (sonarsource.com/products/sonarlint) · Read our introduction to SonarLint
3 SonarQube
By Sonar
SonarQube is a code quality and security platform that automates reviews and verification of human-written and AI-generated code, available as managed cloud or self-hosted server.
Why it is here: It comes after the editor tool because it adds central quality gates on branches and pull requests, which suits teams that want style and smell checks enforced before merge.
- Best for
- Teams enforcing quality gates on pull requests
- Key features
- Analyzes branches and pull requests for bugs, maintainability issues and technical debt across 45+ languages
- Quality gates decide what merges and record every check
- Quality gate results appear in pull requests on major Git platforms
- Server edition can run self-managed, including air-gapped
- Integrates with common editors
- Limits
- The pages we used do not name Kotlin specifically, so teams should confirm Kotlin rule coverage in the vendor documentation. Software composition analysis requires SonarQube Advanced Security.
- Platforms / deployment
- Managed cloud or self-hosted server; Git platform and editor integrations
- Pricing
- See vendor pricing page (not quoted here; facts checked 21 November 2026, Asia/Dhaka)
Official website (sonarsource.com/products/sonarqube) · Read our introduction to SonarQube
4 Codacy
By Codacy
Codacy is a code quality and security platform that enforces coding standards, security scanning and AI coding policies from a single place.
Why it is here: It sits in the multi-language group because it applies one global coding standard across all projects, which helps organizations that run Kotlin next to other stacks.
- Best for
- Organizations applying one coding standard across projects
- Key features
- Coding standards defined once and applied as a global policy across all projects
- AI-powered pull request reviews with fix suggestions and false positive detection
- Supports 49 programming languages and frameworks
- Scans triggered by Git webhooks, so no CI/CD pipeline setup is needed
- Integrates with agents, IDEs, Git, Jira and Slack
- Limits
- The pages we used do not state which Kotlin-specific rules are included, so check the vendor documentation. Much of the documented scope is security and compliance rather than Kotlin style rules.
- Platforms / deployment
- Not stated on official pages
- Pricing
- See vendor pricing page (not quoted here; facts checked 21 November 2026, Asia/Dhaka)
Official website (codacy.com) · Read our introduction to Codacy
5 DeepSource
By DeepSource
DeepSource is an AI code review platform that combines static analysis and AI agents to find security and quality issues on pull requests.
Why it is here: It is placed last because its documented strength is pull request analysis across languages, rather than Kotlin-specific rules or in-editor feedback.
- Best for
- Pull request analysis that surfaces only new issues
- Key features
- Reviews every pull request with deterministic rules plus an AI review agent
- Baseline analysis surfaces only new issues introduced in a pull request
- Can block pull requests that do not meet quality guardrails
- Can automatically run open-source code formatters on commits
- GraphQL API and webhook events; integrates with Jira, GitHub Issues, Slack and Vanta
- Limits
- The pages we used do not list Kotlin among the supported languages, so teams should confirm Kotlin coverage in the vendor documentation. Style enforcement is described through formatters and guardrails rather than a Kotlin rule set.
- Platforms / deployment
- Not stated on official pages
- Pricing
- See vendor pricing page (not quoted here; facts checked 21 November 2026, Asia/Dhaka)
Official website (deepsource.com) · Read our introduction to DeepSource
How we chose these tools
We looked at how well each tool fits Kotlin code smell detection and style enforcement, what capabilities the vendor documents, and what the official pages say about build system, editor and Git platform support. Every fact comes from an official vendor page, and we record the date each page was checked. Where a page does not state something, such as explicit Kotlin support for a multi-language platform, we say so and point readers to the vendor documentation.
The order reflects editorial fit for this use case: Kotlin-native tools come first, then editor-based analysis, then multi-language platforms that work at the pull request and organization level. It is not a statement that one tool is better overall, and a team already standardized on a platform may reasonably start there. The list is built from documentation, not from product trials, so teams should try a candidate on their own codebase before committing.
Order used in this guide: Ordered by depth of Kotlin-specific support, with Kotlin-native tools first and multi-language platforms last.
Frequently asked questions
What is a code smell detection tool for Kotlin?
detekt is an open-source static analyzer for Kotlin that performs code smell analysis. It works with Gradle, Maven and Bazel and supports Android, JVM, JS, Native and Multiplatform projects.
How can a legacy Kotlin project adopt detekt without fixing every issue first?
detekt baselines let legacy projects suppress existing issues while ensuring no new issues are introduced. Individual issues can also be suppressed in source files with @Suppress annotations.
Can I enforce ktlint style rules with detekt?
Yes. detekt provides a wrapper over ktlint as a rule set that can be added to the Gradle configuration.
Which tools give feedback inside the editor?
SonarLint, now called SonarQube for IDE, supports Visual Studio, VS Code, Eclipse and the JetBrains IDE family. Codacy also lists IDE integrations, and SonarQube lists integrations with common editors.
Which tools show only new issues on pull requests?
DeepSource's baseline analysis surfaces only new issues introduced in a pull request, and SonarQube's quality gates show their results in pull requests on major Git platforms. SonarLint offers a focus-on-new-code setting in the editor.
- detekt: detekt.dev, detekt.dev/docs/intro — checked 21 November 2026
- SonarLint: sonarsource.com/products/sonarqube/ide, sonarsource.com/solutions/ai — checked 21 November 2026
- SonarQube: sonarsource.com/products/sonarqube — checked 21 November 2026
- Codacy: codacy.com, codacy.com/about, codacy.com/security — checked 21 November 2026
- DeepSource: deepsource.com, deepsource.com/about, deepsource.com/platform/ai — checked 21 November 2026
Linthelm is independent and not affiliated with the vendors listed. No vendor paid for inclusion or position. Product names belong to their owners. Features and prices change; confirm details on each official website.