gradle-dependency-checker

You can extract resolved dependency versions by executing Gradle dependency-tree commands and parsing the commonMainResolvableDependenciesMetadata configuration to generate a categorized Markdown report grouped by Kotlin, Kotlinx, Skiko, and AndroidX libraries.

Yes, generating Compose Multiplatform dependency reports requires a local Gradle environment to execute dependency-tree commands and Python 3 to run the parser that extracts resolved versions and formats the Markdown output.

Yes, you can automate dependency version checks across multiple Compose Multiplatform versions using included one-click batch processing scripts that iterate through versions and generate reproducible Markdown reports for each.

The best way to verify Kotlin and Skiko version alignment is to parse the Gradle dependency tree using an automated checker that resolves final versions, handles upgrade markers and strict constraints, and groups them into a human-readable Markdown report.

Yes, the dependency checker handles transitive dependency upgrades and strict constraints by parsing the Gradle dependency-tree output to resolve final versions, ensuring accurate reporting of version alignment for Compose Multiplatform projects.