{"id":118734,"date":"2021-08-17T06:50:46","date_gmt":"2021-08-17T06:50:46","guid":{"rendered":"https:\/\/livablesoftware.com\/?p=118734"},"modified":"2021-08-22T12:07:58","modified_gmt":"2021-08-22T12:07:58","slug":"tools-mine-analyze-github-git-software-data","status":"publish","type":"post","link":"https:\/\/livablesoftware.com\/tools-mine-analyze-github-git-software-data\/","title":{"rendered":"20+ tools to help you mine and analyze GitHub and Git data"},"content":{"rendered":"

Any important decision should be grounded on data. This is also true for any decision that affects your software projects. You shouldn’t reach any conclusion regarding the health of your project or the actions to take to improve it without a good look at the data describing the project evolution (in terms of code changes but also regarding the community changes, especially if we are looking at an open-source project<\/a>). Most times, this implies getting some meaningful data out of the Git repository and the code hosting platform (e.g. GitHub<\/a>) where your project resides.<\/strong><\/p>\n

And this is where problems start. It’s actually quite difficult to easily get data out of Git\/GitHub. And if you want to analyze a number of projects (e.g. to know how yours is doing compared to other “similar” ones), it’s almost impossible without investing too many hours. And it’s not because of a lack of interest in mining this data. Plenty of researchers (ourselves<\/a> included) focus on developing new theories on software engineering stemming from mined data<\/a>. There is even a conference devoted to this field<\/a> of research.<\/p>\n

But, so far, I haven’t been able to find a tool that<\/p>\n