OWASP Dependency-Track VS Licensee

I've become interested in SBOM recently, and found there were great tools like https://dependencytrack.org/ for CycloneDX SBOMs, but all I have is SPDX SBOMs generated by GitHub. I decided to have a go at writing my own dependency track esque tool aiming to integrate with the APIs GitHub provides. It's pretty limited in functionality so far, but can give a high level summary of the types of licenses your... - Source: Hacker News / 15 days ago

To detect these types of vulnerabilities, we should first and foremost know our dependencies and versions, and which of them have vulnerabilities. The OWASP Top 10 2021 identifies this need as A06:2021-Vulnerable and Outdated Components. OWASP has several tools for this, including Dependency Check and Dependency Track. These tools will warn about the use of components with vulnerabilities. - Source: dev.to / 25 days ago

Https://dependencytrack.org/ You just need to use one of the various tools out there to scan. - Source: Hacker News / 7 months ago

OWASP Dependency Track - https://dependencytrack.org/. Source: 11 months ago

I actually want to build the same thing you are after, and I think I’ll go for the setup you describe in idea 2. The tool you can use for this is Trivy (https://trivy.dev), have it generate a SBOM and send it to Dependencytrack (https://dependencytrack.org). Source: over 1 year ago

I have a Github repo that hosts my custom package and I've been trying to follow the best Github project conventions possible for this code, including a Readme and so on to make as easy to use as possible. One of these "best practices" includes providing a LICENSE file for clarity and the Github site even uses the licensee package to automatically detect. Source: over 1 year ago