Analyzed
about 1 year
ago.
based on code collected
about 1 year
ago.
Project Summary
Automatically generate JIRA tickets based on open source policy violations or newly reported security vulnerabilities. Track and resolve existing JIRA issues when the violations have been corrected
In a Nutshell, blackduck-jira...
- ...
- ...
- ...
-
...
took an estimated 7 years of effort (COCOMO model)
starting with its first commit in June, 2016
ending with its most recent commit almost 5 years ago
Quick Reference
https://github.com/blackducksoft...
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...
-
...
in 2016, 47% of companies did not have formal process in place to track OS code
-
...
data presented on the Open Hub is available through our API
-
...
55% of companies leverage OSS for production infrastructure
-
...
learn about Open Hub updates and features on the Open Hub blog
30 Day SummaryDec 17 2023 — Jan 16 2024
|
12 Month SummaryJan 16 2023 — Jan 16 2024
|
