No OWASP Dependency-Track videos yet. You could help us improve this page by suggesting one.
Verdaccio might be a bit more popular than OWASP Dependency-Track. We know about 27 links to it since March 2021 and only 19 links to OWASP Dependency-Track. 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'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 / 2 months 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 / 2 months ago
Https://dependencytrack.org/ You just need to use one of the various tools out there to scan. - Source: Hacker News / 9 months ago
OWASP Dependency Track - https://dependencytrack.org/. Source: about 1 year 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
Another option is to publish our package is with azure artifacts, npm with free version public. But if we want to make it private, we need to pay or set up our own private npm repository. In this moment is where Verdaccio comes in to help us. - Source: dev.to / 3 months ago
And finally, we extracted our own Verdaccio setup that we've been using to run our e2e tests in the Nx repo s.t. You can use it for your own plugin development as well. Check out this video for a walkthrough on how this works. - Source: dev.to / 6 months ago
A local install of Verdaccio running next to our app. - Source: dev.to / 10 months ago
You may want to look into setting up a “Private NPM Registry”. My company maintains 5-6 apps and have many shared libraries just like you describe. We use Verdaccio. I don’t know our costs. Source: 12 months ago
All my source code is in GitHub, I run my own private NPM Registry (Verdaccio) for my private packages and it also acts as a cache, and I use pnpm instead of npm. Source: 12 months ago
Snyk - Snyk helps you use open source and stay secure. Continuously find and fix vulnerabilities for npm, Maven, NuGet, RubyGems, PyPI and much more.
npm - npm is a package manager for Node.
FOSSA - Open source license compliance and dependency analysis
Sonatype Nexus Repository - The world's only repository manager with FREE support for popular formats.
WhiteSource - Find & fix security and compliance issues in open source libraries in real-time.
Bytesafe - A better way to control your software supply chain