Analyzed
about 2 hours
ago.
based on code collected
about 2 hours
ago.
In a Nutshell, mergo...
- ...
- ...
-
...
has a well established, mature codebase
maintained by a small development team
with increasing 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 about 2 months 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...
-
...
in 2016, 47% of companies did not have formal process in place to track OS code
-
...
search using multiple tags to find exactly what you need
-
...
65% of companies leverage OSS to speed application development in 2016
-
...
check out hot projects on the Open Hub
30 Day SummaryJun 25 2025 — Jul 25 2025
|
12 Month SummaryJul 25 2024 — Jul 25 2025
|
