Analyzed
about 17 hours
ago.
based on code collected
about 20 hours
ago.
Project Summary
Basic implementation of the __geo_interface__
In a Nutshell, pygeoif...
- ...
- ...
-
...
has a well established, mature codebase
maintained by a average size development team
with increasing Y-O-Y commits -
...
took an estimated 2 years of effort (COCOMO model)
starting with its first commit in July, 2012
ending with its most recent commit 3 days ago
Quick Reference
https://github.com/cleder/pygeoif
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...
-
...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
-
...
by exploring contributors within projects, you can view details on every commit they have made to that project
-
...
65% of companies leverage OSS to speed application development in 2016
-
...
compare projects before you chose one to use
30 Day SummaryMar 25 2024 — Apr 24 2024
|
12 Month SummaryApr 24 2023 — Apr 24 2024
|
