From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

Please use a thread, not individual messages, makes it easier to follow and reference later.

The error you get basically says your repository missed metadata files, so resolution cannot happen.

so you should check if the libraries were correctly published and if not, fix them.

Is it developer who will publish the libraries ?

I suggest you read the docs at <https://docs.gradle.org/current/userguide/dependency_management.html> to get an understanding of dependency management.

you have a dependency on an internal library, and it looks like this library is not published correctly on your company repo.

ok...thank u melix for your response..i am following up with the concerned owners of these repositories...currently i am using cyclondxbom plugin

I tried other option using syft &amp; grype where its not throwing these errors

but here also its scanning same repositories thats mentioned in build.gradle file

any idea why its not throwing these errors when using syft &amp; grype but throwing errors when using cyclonedxbom

Probably the falling tool depends on proper Maven metadata files and the other is not.

I am using cyclonedxbom plugin where its throwing below error -

Unable to resolve POM for com.XXXXX.lwac:lwac:6.7.0-rc5: org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException: Could not resolve all files for configuration ':detachedConfiguration77'.