Analyzed
1 day
ago.
based on code collected
1 day
ago.
Project Summary
Commit patches to Darcs, Git, CVS, Subversion, or Mercurial
In a Nutshell, commit-patch...
- ...
- ...
- ...
-
...
took an estimated 1 years of effort (COCOMO model)
starting with its first commit in August, 2006
ending with its most recent commit about 2 years ago
Quick Reference
https://github.com/caldwell/comm...
GNU General Public License v2.0 only
Permitted
Commercial Use
Modify
Distribute
Place Warranty
Forbidden
Sub-License
Hold Liable
Required
Distribute Original
Disclose Source
Include Copyright
State Changes
Include License
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
-
...
compare projects before you chose one to use
-
...
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
30 Day SummaryDec 14 2025 — Jan 13 2026
|
12 Month SummaryJan 13 2025 — Jan 13 2026
|
