Analyzed
1 day
ago.
based on code collected
2 days
ago.
In a Nutshell, mergo...
- ...
- ...
-
...
has a well established, mature codebase
maintained by a average size development team
with decreasing Y-O-Y commits -
...
took an estimated 1 years of effort (COCOMO model)
starting with its first commit in March, 2013
ending with its most recent commit 9 days ago
Quick Reference
https://github.com/imdario/mergo
BSD 3-clause "New" or "Revised" License
Permitted
Commercial Use
Modify
Distribute
Place Warranty
Forbidden
Hold Liable
Use Trademarks
Required
Include Copyright
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
-
...
you can subscribe to e-mail newsletters to receive update from the Open Hub blog
-
...
65% of companies leverage OSS to speed application development in 2016
-
...
learn about Open Hub updates and features on the Open Hub blog
30 Day SummaryNov 1 2024 — Dec 1 2024
|
12 Month SummaryDec 1 2023 — Dec 1 2024
|
