This is the number of times the source code has been updated. A higher commit count indicates that there are more development activities going into the repository.
This is anyone who has made a change to a GitHub repository. This can include adding code, fixing bugs, uploading new files or writing documentation. The more active contributors a project has, the more likely it will ship new features in the future.
In simple terms, a pull request is a way for contributors to tell the core developers that they have improved the source code and would like the core developer to merge it into the source code. A higher Merged Pull Request figure indicates that more developers are contributing more features and code to the repository.
There are developers who scrutinized the code and found bugs that need to be fixed by the core team. Projects that have no Issue can indicate one of two things: either there is no bug with the repository or no one is interested in the coin to even file an Issue request.
This is the Github version of the Facebook Like button. Similar to the Facebook Like count, a higher Github Star count indicates that more developers appreciate the work that is being done on this code repository.
Developers who are interested in contributing to the source code will also need to fork the source code first before they can contribute. A higher fork count indicates that there are more developers who are interested in copying or contributing to this source code. This indicates a higher developer interest in the source code and potentially some sort of technical innovation where developers are interested in forking the code to launch their own token.
Best Of 100
These are custom categories that are made up of the metrics above. Each category will contain some of the metrics, which we regard as “key metrics”.
To be featured in a specific category, projects will be ranked by their category score. The category score for a project will be calculated by averaging rank score from their corresponding key metrics, follow this formula:
Category Score = Average Rank Score (of every key metric within the category)
(The category score will be re-evaluated weekly)
Rank Score: project that has Rank #1( the highest) will have a rank score of 100, and the project with Rank #100 (lowest) will have a rank score equal to 1. If a key metric is not in the top 100, the rank score will be 0 pts. by default (for example: Rank #101 or Rank #240 also have the same rank score, which is 0)
Then, each project in the category will be ranked based on their category score.
Apart from the features above, Dev3map also provides a different approach on developer activity. This time, through the scope of a developer, thanks to Developer Profile.
For each project that Dev3map is tracking, the corresponding list of developers will also be tracked and their contributions are illustrated on their Developer Profile.
With Developer Profile, you can: discover who are the key factors of a project, how many organizations they’ve involved, which fields they are specialized on and more.