No features have been listed yet.
OWASP Dependency-Track is ideal for security-conscious development teams, DevSecOps professionals, and organizations with a strong focus on application security. It is particularly beneficial for those using a wide array of open-source components who need to ensure ongoing compliance with security standards.
No OWASP Dependency-Track videos yet. You could help us improve this page by suggesting one.
Based on our record, OWASP Dependency-Track seems to be a lot more popular than Licensee. While we know about 19 links to OWASP Dependency-Track, we've tracked only 1 mention of Licensee. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
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 2 years ago
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 / about 1 year 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 / about 1 year ago
Https://dependencytrack.org/ You just need to use one of the various tools out there to scan. - Source: Hacker News / over 1 year ago
OWASP Dependency Track - https://dependencytrack.org/. Source: about 2 years 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 2 years ago
FOSSA - Open source license compliance and dependency analysis
Snyk - Snyk helps you use open source and stay secure. Continuously find and fix vulnerabilities for npm, Maven, NuGet, RubyGems, PyPI and much more.
ScanCode - ScanCode is a suite of utilities used to scan a codebase for license, copyright and other...
Ninka - License identification tool for source code.
WhiteSource - Find & fix security and compliance issues in open source libraries in real-time.
Slic - Speedy LIcense Checker and associated tools.