No OWASP Dependency-Track videos yet. You could help us improve this page by suggesting one.
Artifactory might be a bit more popular than OWASP Dependency-Track. We know about 20 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 / 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 kind of hate it, but Artifactory seems popular at companies: https://jfrog.com/artifactory/. Source: 10 months ago
When not providing all dependencies yourself, you might suffer from people deleting the packages you depend on (IMHO a very rare scenario). If it is really that critical (hint: usually it isn't), create a local mirror of Pypi (full or only the packages you need). Devpi, Artifactory, etc. Can do that or you just dump the necessary files into Cloud storage, so you have a backup. Source: about 1 year ago
Operate a pull-through cache registry, like Artifactory or the open source reference Docker registry. This will allow you to pull images from Docker Hub less frequently, improving your chances of staying under the anonymous usage limit. - Source: dev.to / about 1 year ago
Like suppose for a second that . . . Idk . . . a product team wants our ci workflows to start using Artifactory. Okay great, I don't know Artifactory integration but I'm going to tell them "Sure, I'll get right on that.". Source: about 1 year ago
If these "assets" have an independent release schedule I would treat them separately (especially if they are externally provided). If they are not built from source then treat them as artefacts, they don't belong in git. You can store the in an artefact repository (like Artifactory of Nexus) or (as u/nekokattt points out) in something like S3. Source: over 1 year 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.
Sonatype Nexus Repository - The world's only repository manager with FREE support for popular formats.
FOSSA - Open source license compliance and dependency analysis
Cloudsmith - Cloudsmith is the preferred software platform for securely storing and sharing packages and containers. We have distributed millions of packages for innovative companies around the world.
WhiteSource - Find & fix security and compliance issues in open source libraries in real-time.
Git - Git is a free and open source version control system designed to handle everything from small to very large projects with speed and efficiency. It is easy to learn and lightweight with lighting fast performance that outclasses competitors.