cyclonedx-gradle-plugin VS scancode-toolkit

There is a CyconeDX plugin available for Gradle. Just like the Maven plugin we discussed earlier, the Gradle plugin is released by the CycloneDX organization on Github with some of the same maintainers as the Maven plugin.

I am not sure if it fits your use case https://github.com/CycloneDX/cyclonedx-gradle-plugin

OP - rather than jumping in with a “solution”, I would be Irving you to use this as an opportunity for change in your company to improve the governance around software installation in your company (a software catalog and white listing applications would be the best approach), reduce the exposure of licensing costs (or pirated software) in your environment and simplify your ongoing support requirements. Software Bill Of Materials software such as Cyclone DX as a possible solution to collate the information along with vulnerability information, to focus on the known vulnerabilities vs oldest software would be my recommendation. This is a priority in the US under the Executive Order 14208 to improve the nations’s cyber security - The minimum requirements for a Software Bill Of Materials.

I think CycloneDX [1] is the go-to SBOM specification these days.

[1] https://cyclonedx.org/

Hey, pabs3! Actually this is not using a rolling checksum for detection but rather a combo of language model, checksums, automatons, bitvectors, inverted indexes and multiple sequences alignment (e.g. a specialized diff). I put some docs there to explain the approach at ahttps://github.com/nexB/scancode-toolkit/blob/develop/src/li...

If you're concerned about licensing in your dependencies, use a license scanner like scancode toolkit. Similar scanners are available in products like JFrog Artifactory or GitLab (paid versions)