Analyzed
11 months
ago.
based on code collected
11 months
ago.
Project Summary
Dependency-Check is a utility that detects publicly disclosed vulnerabilities in project dependencies.
In a Nutshell, DependencyCheck...
- ...
- ...
-
...
has a well established, mature codebase
maintained by a very large development team
with decreasing Y-O-Y commits -
...
took an estimated 40 years of effort (COCOMO model)
starting with its first commit in September, 2012
ending with its most recent commit 11 months ago
Quick Reference
Organization:
https://github.com/jeremylong/De...
Apache License 2.0
Permitted
Commercial Use
Modify
Distribute
Place Warranty
Sub-License
Private Use
Use Patent Claims
Forbidden
Hold Liable
Use Trademarks
Required
Include Copyright
State Changes
Include License
Include Notice
These details are provided for information only. No information here is legal advice and should not be used as such.
Project Security
Vulnerabilities per Version ( last 10 releases )
There are no reported vulnerabilities
Project Vulnerability Report
Security Confidence Index
Poor security track-record
Favorable security track-record
Vulnerability Exposure Index
Many reported vulnerabilities
Few reported vulnerabilities
Did You Know...
-
...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
-
...
search using multiple tags to find exactly what you need
-
...
use of OSS increased in 65% of companies in 2016
-
...
you can subscribe to e-mail newsletters to receive update from the Open Hub blog
30 Day SummaryDec 19 2023 — Jan 18 2024
|
12 Month SummaryJan 18 2023 — Jan 18 2024
|
Static Analysis ( Generated by Coverity Scan for jeremylong/DependencyCheck )
Repository URL: https://github.com/jeremylong/DependencyCheck
Version: main
- 2024-01-13
- Last Analyzed
- 49,311
- Lines of Code Analyze
- 3.48
- Defect Density
Defects by status for current build
- 368
- Total defects
- 125
- Outstanding
- 240
- Fixed
CWE Top 25 defects
| ID | CWE-Name | Number of Defects |
|---|---|---|
| 327 | Use of a Broken or Risky Cryptographic Algorithm | 5 |