Analyzed
about 5 hours
ago.
based on code collected
about 6 hours
ago.
Project Summary
Collection of QA checks for ebuild repositories; far faster then portage (~5 minute full tree check for a hot cache) and a fair bit more comprehensive.
Badges
In a Nutshell, pkgcheck...
- ...
- ...
-
...
has a well established, mature codebase
maintained by a average size development team
with decreasing Y-O-Y commits -
...
took an estimated 6 years of effort (COCOMO model)
starting with its first commit in May, 2006
ending with its most recent commit 12 days ago
Quick Reference
https://github.com/pkgcore/pkgcheck
GNU General Public License v2.0 or later
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...
-
...
55% of companies leverage OSS for production infrastructure
-
...
anyone with an Open Hub account can update a project's tags
-
...
in 2016, 47% of companies did not have formal process in place to track OS code
-
...
you can subscribe to e-mail newsletters to receive update from the Open Hub blog
30 Day SummaryMay 26 2025 — Jun 25 2025
|
12 Month SummaryJun 25 2024 — Jun 25 2025
|
