Analyzed
about 21 hours
ago.
based on code collected
1 day
ago.
In a Nutshell, Ruby-GPGME...
- ...
- ...
-
...
has a well established, mature codebase
maintained by a large development team
with stable Y-O-Y commits -
...
took an estimated 2 years of effort (COCOMO model)
starting with its first commit in October, 2006
ending with its most recent commit 28 days ago
Quick Reference
https://github.com/ueno/ruby-gpgme
MIT
Permitted
Commercial Use
Modify
Distribute
Place Warranty
Use Patent Claims
Forbidden
Sub-License
Hold Liable
Required
Distribute Original
Disclose Source
Include Copyright
State Changes
Include License
Include Install Instructions
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
-
...
anyone with an Open Hub account can update a project's tags
-
...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
-
...
you can subscribe to e-mail newsletters to receive update from the Open Hub blog
30 Day SummaryMar 24 2024 — Apr 23 2024
|
12 Month SummaryApr 23 2023 — Apr 23 2024
|
