Hi Tamás, Maarten, and Gary, Thank you for the examples and guidance. After looking through toolbox:tree, tree-find, and the Resolver documentation, I understand the problem space much better now.
My initial idea was focused on finding why a dependency is present, but I see that much of this is already covered by existing tools. The more interesting gap seems to be explaining Maven's resolution decisions: - Why was this version selected? - Which dependency management/BOM influenced it? - Which competing versions were considered but not selected? - Which mediation rule led to the final result? >From the Resolver documentation, it seems this information already exists during the collect/transform phases. The challenge would be exposing it in a way that helps users understand *why* Maven reached a result, rather than only showing the final dependency graph. I am not attached to the original `dependency:insight` idea if there is a better direction. I would like to explore something that provides real value to Maven users and fits the project's needs. If there are other related areas you think would be more valuable to investigate, I would be happy to explore them as well. Thanks again for the guidance. Best regards, Hitesh
