This message was deleted.

You can look at a project's configuration-dependent`ResolvedComponentResult` and traverse its graph-like structure to check for dependencies - you'll be able to do whatever you want there

Check out the implementation in https://github.com/dropbox/dependency-guard/blob/main/dependency-guard/src/main/ko[…]ox/gradle/plugins/dependencyguard/internal/DependencyVisitor.kt Note: You'll want to know what configuration (i.e.

runtimeClasspath

) you are targeting.

internal fun ConfigurationContainer.getResolvedComponentResult(configurationName: String): Provider<ResolvedComponentResult>? = this
    .findByName(configurationName)
    ?.incoming
    ?.resolutionResult
    ?.rootComponent

You can use this provider as an input to the task, and use it later to visit the dependencies

or https://github.com/jraska/modules-graph-assert

Thank you all, I’ll take a look a these solutions.