Analyzed
1 day
ago.
based on code collected
1 day
ago.
Project Summary
After the installation of a source package with "./configure && make && make install", one is usually left with having no idea of what it was installed and where it all went, making it difficult to uninstall the package in the future.
Paco was written to solve this problem in a quite simple fashion.
In a Nutshell, paco...
- ...
- ...
- ...
-
...
took an estimated 7 years of effort (COCOMO model)
starting with its first commit in April, 2006
ending with its most recent commit over 11 years ago
Quick Reference
svn://svn.code.sf.net/p/paco/cod...
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...
-
...
in 2016, 47% of companies did not have formal process in place to track OS code
-
...
data presented on the Open Hub is available through our API
-
...
65% of companies leverage OSS to speed application development in 2016
-
...
anyone with an Open Hub account can update a project's tags
30 Day SummaryApr 2 2024 — May 2 2024
|
12 Month SummaryMay 2 2023 — May 2 2024
|
