About OpenLogic Certification

The purpose of OpenLogic Certification scores is to help enterprises evaluate the most appropriate open source packages for use within the enterprise.

About OpenLogic Certification Scores

OpenLogic conducts a rigorous 42-point certification process on each open source package that is available on OpenLogic Exchange (OLEX). As part of this process, we create scores that rate open source packages in three areas: Adoption, Community/Viability and Legal. We then average these three scores for an Overall certification score.

Adoption – this score indicates how broadly the open source package is used in enterprises.
Community –this score indicates the strength and robustness of the project’s community.
Licensing – this score indicates the relative legal and license complexity.
Overall – this score is an overall certification score that is an average of the three component scores.

How Scores Are Calculated

Scores can range between one and five stars. To calculate the certification scores, we start by collecting raw data and statistics on each project. In some cases, we are not able to obtain all of the data needed using our standard processes. In this case, we may estimate the raw data or leave it blank. While we tried not to penalize a project for missing data, blank or estimated raw data may impact the overall score. We then apply a set of rules, created by OpenLogic, to translate the raw data into a score between one and five.

Data Used to Calculate the Scores

Adoption
Adoption is calculated on several factors that predict how widely the package is used. Factors include statistics like the number of downloads over the past year and the number of OpenLogic enterprise customers using the package. For packages where we cannot find exact information, we may estimate data or leave it blank. Estimates or blank data may impact the score.

Community
This score is based on factors such as how long the project has been around, the size of the developer community and various activity metrics like number of code commits, bug fixes, and forum posts. For packages where we cannot find information, we may estimate data or leave it blank. Estimates or blank data may impact the score.

Licensing
This score is based on the number of licenses, the types of licenses, license conflicts and any history of legal actions.

Disclaimers

These scores are calculated based on data obtained from public sources. These sources of data cannot be guaranteed by OpenLogic and may not be accurate. OpenLogic may not use every possible public source of data. OpenLogic uses its own formulas and methodology to calculate the scores. This methodology may not be appropriate for your use. These scores should be used in conjunction with your own research to determine open source packages that are appropriate for your particular use. They should not be considered a replacement for your own due diligence.

Feedback