[DarpalRating] We went through 133 Blockchain projects Github, Here’s our Code Audit Report for February DPRating Follow Mar 16, 2018 · 3 min read

March 15th, 2018; by Darpal Rating team

Translated by LI Qingkun &Tyler Garant

We have received a lot of feedback since the release of our last code auditing report in January . We have improved our auditing method as follows:

Added changes in ranking, so that readers can easily see how projects are progressing compared to the previous month.

Added more libraries into our analytics. Last month we only analyzed the popularity and number of commits of the 2 most active libraries for projects with more than three libraries — this month we have included all libraries into our observation. We have also fixed the popularity of the libraries forked from Bitcoin, such that the number of forks is no longer calculated as part of popularity.

How do we rate?

Popularity of the Library

Popularity of the Library is defined as the mean number of Watch, Star and fork. Very High: > 500, High: between 100 and 500, MediumL between 20 and 100, Low: Below 20.

Number of Contributors

Number of Contributors: The number of contributors that have committed code in the last month. High: More than 12, Medium: between 6 and 12, Low: Below 6.

Release Frequency

Release Frequency: We took the version release frequency of Bitcoin and Ethereum, 14.25 days for a new release, as a reference value. We then divide the number of average days spent for a new release by 14.25 to get a release frequency score. High: below 2, Medium: between 2 and 4, Low: above 4.

e.g. The main chain of EOS has been released 35 times from 4/2/2017 to 3/1/2018, for an average of 9.51 days between new releases. This divided by 14.25 is 0.71, so the release frequency of EOS would be considered high.

Type of commit

A1: Continuously, steadily developing new features

A2: Fixing Bugs and testing after new feature developments

A3: Releasing few new features based on initial commitment and changing configurations.

B: Fixing bugs and tasing for Devops

C: Changing configuration for Devops

D; Cannot be defined in any above category

The overall rating ranges from 1 to 5

Popularity of the library: 1 point for Very High, 0.5 points for High, no point for Middle or Low;

Number of Contributors: 1 point for High, 0.5 point for Medium, no point for Low

Release frequency: 1 point for High, 0.5 point for Medium, no point for Low

Number of Commits: 1 point for over 200 commits, 0.5 point for between 100 and 200 commits, no point for between 30 and 100 or below 30

Commit type: 1 point for A1 or A2, 0.5 point for A3, no point for B, C and D

We only audit core libraries. The definition of core library varies for each project.

For projects that have a main chain, (e.g. public chain and consortium chain) we only evaluate the main chain. The current development phase of the project does not affect our evaluation. For projects that do not have a main chain, we choose to evaluate their core libraries.

Here is our result:

If you like this review, please follow our Medium Channel. For more:

Twitter: https://twitter.com/DarpalRating

Telegram: t.me/DarpalRating