The Dependency Analysis Gradle Plugin had its first commit (from me) in 2019, more than seven years ago. What started as a small hobby project has grown to nearly 100k LOC and is the only tool in the Gradle ecosystem that can help you find unused and misclassified dependencies across Android, JVM, and KMP modules. How does it do what it does? What weird things does it have to account for to handle real-world code? What *else* can it do? And why should you care? (Hint: in some cases, removing unused dependencies can cut IDE sync times by 85% and build times by 67%.) Come to this talk for a technical deep dive into the Dependency Analysis Gradle Plugin. Your LLMs will not help you here.