Gradle Lighthouse — Architecture Health Scoring for Android & KMP

Health scoring, dependency analysis, build performance auditing, and 20+ architectural checks.
Zero-config. Actionable. CI/CD ready.

Get Started — Free

plugins { id("io.github.dev-vikas-soni.lighthouse") version "2.3.1" }

Stop Guessing About Your Build Health

Most teams know they have technical debt — but not which modules are slowing them down, where architecture boundaries are breaking, or why builds are getting slower.

Gradle Lighthouse gives you a single command audit with architecture scoring, module graph visualization, and a clear “Path to 90” improvement roadmap.

Key Capabilities

🏗️ Architecture Health Score

Transparent scoring across Architecture, Security, Build Performance, Dependency Hygiene, Complexity, Modernization, and more.

🌌 Galaxy Graph

Interactive module dependency visualization with cycle detection, impact analysis, and refactoring sandbox.

📈 Path to 90

Prioritized improvement roadmap showing exactly which fixes give the biggest score gains.

🔧 CI/CD Ready

SARIF, JUnit XML, HTML reports. Works with GitHub Actions and modern pipelines. Configuration cache compatible.

Why Teams Need Lighthouse

It answers the questions every Android/KMP tech lead asks:

  • Which modules are architectural bottlenecks?
  • Where are the hidden dependency cycles?
  • Why is our build getting slower over time?
  • How do we compare against industry benchmarks?

Quick Start

plugins {
    id("io.github.dev-vikas-soni.lighthouse") version "2.3.1"
}

Run: ./gradlew lighthouseAudit lighthouseAggregate

Add Gradle Lighthouse to Your Build

Perfect Companion to LeakLens

Use Gradle Lighthouse for build-time architecture health and LeakLens for runtime memory correctness — together they form a complete quality platform for modern Android development.

GitHub Repository • Roadmap • LeakLens

Comments

Post a Comment

Featured Articles

Play Store Uploads with Fastlane Supply - 4

Image
If you’ve ever manually uploaded an APK or AAB to the Google Play Store, you know it can be a tedious process. From filling out all the necessary metadata to selecting the correct APK version, it can feel like a lot of repetitive work. But with Fastlane Supply , you can automate this entire process — making your app releases smoother, faster, and error-free. In this section, we’ll explore how Fastlane Supply works and how to set it up to upload your Android app directly to the Play Store with ease. Step 1: Set Up Google Play API Access Before you can upload your app with Fastlane Supply , you need to set up Google Play API access . This ensures that Fastlane can communicate with the Play Store and upload your APK or AAB. Here’s how you can set up API access: Create a Google Cloud project : Go to the Google Cloud Console. Create a new project. Enable the Google Play Developer API : In the Cloud Console, search for and enable the Google Play Developer API . Create a service account ...
Read more

Cracking Android SDE2/SDE3 Interviews in 2026: Deep Dives, Code, Follow-ups | Part-2

Image
  Architecture & Patterns Find Part -1 From Here Find Part -3 From Here 21. MVVM vs MVI? Interviewer: Compare MVVM and MVI — when choose MVI? Candidate: MVVM: View observes ViewModel state (StateFlow/LiveData), unidirectional updates. Simple for CRUD. MVVM (Model–View–ViewModel) How MVVM works View observes state from ViewModel ViewModel exposes data via LiveData or StateFlow View calls functions directly on ViewModel State is often split across multiple variables Typical MVVM flow View → ViewModel.method() ViewModel → update LiveData / StateFlow View ← observes updates Example MVVM pattern class ProfileViewModel : ViewModel () { val loading = MutableStateFlow( false ) val profile = MutableStateFlow<Profile?>( null ) val error = MutableStateFlow<String?>( null ) fun loadProfile () { loading.value = true // fetch profile } } Problems MVVM faces at scale State is scattered Hard to know which user action caused ...
Read more

JIT vs AOT Compilation | Android Runtime

Image
           D id you ever think, what happens when you install your app in your Android device, it shows INSTALLING for fraction of second and app get opens. What happens exactly behiend the scene? Found Interesting???? Cool !!! let’s clear all the doubt in this blog. You would have definetely read the buzz words JIT(Just-in-time) and AOT(Ahead of time) at many ocassions. We’ll dig it down in details in this article, stay tuned…. Android apps run on Android Runtime (ART) , which replaced Dalvik since Android 5.0 (Lollipop). ART supports both JIT (Just-In-Time) Compilation and AOT (Ahead-Of-Time) Compilation to improve performance and efficiency. JIT (Just-In-Time) Compilation How it Works: Compiles bytecode into native machine code at runtime (when the app is executed). Stores frequently used methods in memory to speed up subsequent executions. Advantages: Faster app installation because it doesn’t require full compilation beforehand. Reduces s...
Read more

From ‘Master’ to ‘Main’: The Meaning Behind Git’s Naming Shift

Image
                             Git changed its default branch name from master to main due to concerns about inclusivity and to remove references to terms with problematic historical connotations. The term master has been associated with slavery, and many tech communities sought to use more neutral and inclusive language. Reason for the Change: Inclusivity & Sensitivity- Many organizations aimed to remove racially charged terminology from software development. Consistency Across Communities- Other projects and platforms, such as Github, Gitlab, and software frameworks, also made similar changes. Modern Naming Conventions- main is a cleaner and more intuitive name, as it represents the primary branch of a repository. Interesting Facts —  It wasn’t originally about slavery  — The term Git did not originate from the master/slave concept used in computing. It likely came from Bitkeeper , a version contro...
Read more

Optimize Jetpack Compose: Performance & Best Practices

Image
      Jetpack Compose offers a declarative approach to building UIs in Android. However, like any UI framework, optimization is key to achieving smooth performance and a great user experience. This detailed guide expands on the provided checklist, offering in-depth explanations and practical code examples for each optimization technique. I. Core Principles: Laying the Foundation for Performance Use Stable Types:  Compose relies on stable types to efficiently track changes and minimize recompositions. A stable type guarantees that if two instances of the type are equal according to  equals() , they will always be equal. Using unstable types can force unnecessary recompositions.   // Stable data class (recommended) data   class   User ( val  name: String,  val  age:  Int ) // Unstable list (avoid directly in Compose state) // Use SnapshotStateList instead val users = remember { mutableStateListOf<User>() } // Cor...
Read more