Keep your codebase tidy — but don't rush to delete
In my experience, removing unused code is one of those tasks that pays off slowly but significantly. This plugin helps you find candidates safely: classes, top-level Kotlin functions, resources, and even declared Gradle dependencies that appear unused.
It's lightweight, runs on compiled classes (so results reflect the actual bytecode), and can be run locally or in CI. Use it as a guide — not an automatic refactor tool.
Quick start
plugins {
id("io.github.arya458.dead-code-detector") version "0.0.3"
}
# run
./gradlew deadCodeDetector
Default report: build/reports/dead-code-detector/report.txt
What this plugin reports
- Dead classes, top-level functions, and top-level fields
- Unused resource files in your resources directory (optional)
- Unused Gradle dependencies declared in your module
Note: reflection, JNI, or frameworks using runtime binding (DI) may make code look unused. Use keep rules to avoid false positives.