# detekt Published articles for detekt. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 51 Detekt Rules for Koin: Catch Anti-Patterns Your Compiler Misses DevFeed: [51 Detekt Rules for Koin: Catch Anti-Patterns Your Compiler Misses]() Original publisher: [Read original article]() Author: Kirill Rozov Published: 2026-03-02T08:17:18Z Content type: tutorial Language: en Sources: [Stories by Kirill Rozov on Medium]() Topics: [koin](), [Android](), [ci]() Tags: [analysis](), [android](), [best-practices](), [ci](), [dependencies](), [detekt](), [errors](), [koin](), [kotlin](), [kotlin-multiplatform](), [tests]() ### AI overview This article explains how the detekt-rules-koin Detekt extension identifies Koin dependency-injection anti-patterns that compile successfully but can fail at runtime. It covers misuse of get(), service-locator access through KoinComponent, singleton registration for mutable use cases, and installation in an existing Detekt setup. ### Source excerpt Your Koin module compiles. Unit tests pass. CI is green. Then production crashes with NoBeanDefFoundException on first launch -- and the offending line has been sitting in your codebase for weeks. Koin's runtime graph resolution means the compiler never sees these bugs; it only surfaces them when Koin tries to wire everything together. No red underlines, no warnings, no build failures -- just a crash on a user's device. This is the fundamental tension with Koin: its DSL is concise and readable, but none of the structure it creates is visible to the type system. The three examples below compile without errors on any Android project. All three will cause real problems at runtime. Static analysis is the standard answer to this class of problem -- but generic Detekt rules were not written with Koin's semantics in mind. A rule that flags unused variables or improper nullability checks has no concept of a Koin scope, a module definition block, or the difference between single and factory. What you need is a rule set that understands Koin. That's exactly what detekt-rules-koin provides. Problem 1 -- `NoGetOutsideModuleDefinition`// ❌ get() called outside a Koin module - compiles, crashes at runtime class UserRepositoryImpl : UserRepository { // KoinComponent not implemented, no scope active private val db: AppDatabase = get() private val api: UserApi = get() } get() is only valid inside a Koin module definition block, where the Koin container is active and providing dependencies. Calling it here triggers IllegalStateException: KoinApplication has not been started -- or silently resolves to the wrong scope -- depending on how your app is wired. Problem 2 -- NoKoinComponentInterface// ❌ Repository using Service Locator via KoinComponent class UserRepository : KoinComponent { private val db: AppDatabase by inject() private val api: UserApi by inject() fun getUser(id: String) = api.fetchUser(id) }// ✅ Constructor injection - dependencies are explicit and testable class UserRepository ## Using Google Gemini in a Python Script to Fix Static Analysis Issues DevFeed: [Using Google Gemini in a Python Script to Fix Static Analysis Issues]() Original publisher: [Read original article]() Author: blundell Published: 2025-09-23T16:24:26Z Content type: tutorial Language: en Sources: [Blundell]() Topics: [Artificial Intelligence](), [Code quality](), [Python](), [Google](), [Large Language Model](), [Refactoring](), [context window]() Tags: [ai](), [androiddev](), [build](), [code-quality](), [context-window](), [detekt](), [gemini](), [google](), [intermediate](), [python](), [refactoring](), [reference](), [reference-ai-androiddev-detekt-gemini]() ### AI overview This tutorial describes building a Python script that uses Google Gemini to automatically fix static analysis issues. It discusses the limitations of one-shot fixes, including LLM context-window limits, and explains how to curate the context sent to the model. ### Source excerpt Tired of fixing endless linting errors? What if an AI could do it for you? In this post, we'll walk through how to build a Python script that uses Google's Gemini to automatically fix static analysis issues, exploring the process and the lessons learned along the way. This is a journey from a simple idea [...] The post Linting, Automated: AI-Powered Static Analysis with Gemini first appeared on Blundell. ## Static Code Analysers DevFeed: [Static Code Analysers]() Original publisher: [Read original article]() Published: 2024-01-22T00:15:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [detekt](), [Kotlin](), [Programming](), [code reviews](), [compilers]() Tags: [android](), [code-reviews](), [compilers](), [detekt](), [generics](), [java](), [jvm](), [kotlin](), [workshop-learning-programming]() ### AI overview This tutorial introduces static analysis as a way to identify bugs and recurring code patterns without running the code. It explains how static analysers can automate and enforce coding patterns in large Kotlin codebases, then begins a practical walkthrough of detekt, a popular Kotlin static analyser. ### Source excerpt All you need to know about Static Code Analysers and Detekt. ## Setting up precommit lints for all team members DevFeed: [Setting up precommit lints for all team members]() Original publisher: [Read original article]() Author: Dmitry Samoylenko Published: 2020-12-06T00:00:00Z Content type: tutorial Language: en Sources: [Dmitry Samoylenko - Android Developer Blog]() Topics: [Script](), [Git](), [Unix](), [Command-line interface](), [Windows]() Tags: [androidstudio](), [command-line](), [detekt](), [git](), [pre-commit](), [script](), [unix](), [windows]() ### AI overview A tutorial on configuring Detekt and ktlint, running lint checks before each Git commit with a pre-commit script, and sharing the setup with team members. The script supports Unix systems and requires edits for Windows. ### Source excerpt What lints? ## Hello8Ball: Exploring Coroutine Testing with a Kotlin Sampler App DevFeed: [Hello8Ball: Exploring Coroutine Testing with a Kotlin Sampler App]() Original publisher: [Read original article]() Published: 2019-11-23T21:36:11Z Content type: tutorial Language: en Sources: [maiatoday]() Topics: [Coroutines](), [Testing](), [test](), [CircleCI](), [test-coverage](), [App]() Tags: [circleci](), [code](), [code-coverage](), [coroutine-testing](), [coroutines](), [detekt](), [jacoco](), [kotlinx](), [test](), [testing](), [tests]() ### AI overview Hello8Ball is a toy sampler app for exploring coroutine testing in Kotlin. It simulates an 8 Ball and includes examples involving network calls, calculations, password generation, synonym lookup, and prime-number checks. The repository includes tests using kotlinx-coroutine-test, CircleCI test execution, detekt, JaCoCo coverage, and a branch converted to JUnit 5. ### Source excerpt A sampler app to explore Coroutine testing. This is a toy app that simulates an 8 Ball. It can answer questions, find synonmyms, generate a password or check if a number is prime. It was created to make a situation where it makes sense to use coroutines to e.g. go on the network or make a calculation. Then I added tests for all the pieces using kotlinx-coroutine-test. As a bonus the repo is set up to run the tests on CircleCi. It has detekt setup and jacoco code coverage. There is also a branch where all the tests are converted to junit5. Devfest 2019 video This is the companion repo to the KotlinEveryWhereZA 2019 and DevFestZa 2019 talk. Slides are in the repo. code