dependency-track
DependencyCheck
Our great sponsors
dependency-track | DependencyCheck | |
---|---|---|
18 | 11 | |
2,329 | 5,878 | |
6.2% | - | |
9.8 | 9.5 | |
4 days ago | 3 days ago | |
Java | Java | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dependency-track
-
Show HN: Pre-alpha tool for analyzing spdx SBOMs generated by GitHub
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 repository dependencies use, and let you drill down into potentially problematic ones.
Written in NextJS + mui + sqlite, and using another project of mine to generate most of the API boilerplate/glue (https://github.com/mnahkies/openapi-code-generator)
-
SQL Injection Isn't Dead Yet
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.
- Dependency-Track
-
Krita fund has 0 corporate support
https://dependencytrack.org/
You just need to use one of the various tools out there to scan.
-
Friends - needs help choosing solution for SBOM vulnerability
OWASP Dependency Track - https://dependencytrack.org/
-
An Overview of Kubernetes Security Projects at KubeCon Europe 2023
Dependency-Track
-
software inventory of my ECS tasks
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).
-
The ultimate guide to Java Security Vulnerabilities (CVE)
If you like Dependency-Track, consider moving to Dependency-Track ( https://dependencytrack.org ), which makes administration much easier.
-
Is there any news about 64 bit Steam?
Even if you roll up the sleeves and add the feature yourself there is no guarantee it will be accepted upstream and you should always be prepared for the possibility of wasting time.
-
The SBOM Frenzy Is Premature
I don't quite understand the deployment issue. I mean, I understand people might not be tracking what's deployed, but I don't understand what is missing for it to be happening today, other than will.
For example: I build some software into a Docker image, version tag it, sign it, and generate an SBOM for it. That image goes into production with signature validation. Even if I've included 100 jar files in there, I should know exactly which ones I have. I can upload the SBOM to my DependencyTrack[1] instance to so over time no dependencies have vulnerabilities I'm not aware of.
What doesn't work in that scenario? What scenarios can't conform to that one?
[1] https://dependencytrack.org
DependencyCheck
- OWASP dependency check (<9.0.0) could fail to work after Dec 15th, 2023
-
How To Secure Your JavaScript Applications
Use Security Tools: To identify known vulnerabilities in your project's dependencies, you can utilize commands like npm audit or employ third-party security scanners such as DependencyCheck or Dependabot. These tools thoroughly analyze the dependency tree and offer actionable insights to assist you in resolving any identified vulnerabilities.
-
Do you use dependency analysis and vulnerability detection tools?
OWASP DependencyCheck - a really decent tool for scanning your project for vulnerable dependencies. It is actively developed and updated and up to date with the most latest vulnerabilities. Sometimes it can be a pain in the ass, though. Some security researchers and such find a vulnerability, publish it and the next day our CI/CD pipelines fail (the dependency check build step prevents the code from going to production). And not always there is a fix available. So, some vulnerabilities have to be ignored, temporarily. Also, to be able to ignore a vulnerability one has to do a fast risk assessment. And that will require from him to read about the vulnerability and decide if it is safe to be ignored or some different workaround must be found.
-
The ultimate guide to Java Security Vulnerabilities (CVE)
The ultimate guide somehow fails to mention the best CVE checker: https://github.com/jeremylong/DependencyCheck
-
Is Clojure suitable for my use cases?
We run https://github.com/jeremylong/DependencyCheck over our dependency tree regularly, via this Clojure wrapper: https://github.com/clj-holmes/clj-watson which tells us the dependency tree path to each item that has a CVE and also the version in which the CVE is addressed, if known.
-
Gitlab community dependency scanning
We use OWASP dependency-check and pass reports to SonarQube.
-
Security in CICD / DevSecOps
From OWASP for those class of tools you could look into DependencyCheck and DependencyTrack
- Is there a tool to track CVEs for the software that we use?
-
Does anybody know any good materials for java defensive coding please?.
DependencyCheck is an open source tool that checks for vulnerabilities in dependencies used within a project. While it is a reactive tool, it's an important one since the code a developer writes is not the only code an application uses.
-
Are there any tools I can use to safely upgrade my Nuget packages? What are some strategies I can incorporate?
One more aspect to consider, although I know it is not the primary ask of the post, is to be sure and run something like dependency check on your repository. There are quite a few vulnerabilities being injected through the packaging process these days.
What are some alternatives?
trivy - Find vulnerabilities, misconfigurations, secrets, SBOM in containers, Kubernetes, code repositories, clouds and more
SonarQube - Continuous Inspection
scancode-toolkit - :mag: ScanCode detects licenses, copyrights, dependencies by "scanning code" ... to discover and inventory open source and third-party packages used in your code. Sponsored by NLnet project https://nlnet.nl/project/vulnerabilitydatabase, the Google Summer of Code, Azure credits, nexB and others generous sponsors!
opencve - CVE Alerting Platform
gitlab
openvas-scanner - This repository contains the scanner component for Greenbone Community Edition.
sbt-dependency-check - SBT Plugin for OWASP DependencyCheck. Monitor your dependencies and report if there are any publicly known vulnerabilities (e.g. CVEs). :rainbow:
uml-reverse-mapper - Automatically generate class diagram from code. Supports Graphviz, PlantUML and Mermaid output formats.
ort - A suite of tools to automate software compliance checks.
slsa - Supply-chain Levels for Software Artifacts
cyclonedx-bom-repo-server - A BOM repository server for distributing CycloneDX BOMs
ArchUnit - A Java architecture test library, to specify and assert architecture rules in plain Java