Number of lines of code? Size of methods? Number of commits? How much you like them?
An about page with the grading methodology should probably be the next thing you publish. Also, in my mind the historical breakdown is irrelevant. I couldn't care less if the project sucked two weeks ago if they re-factored and are now "a" quality. Of course, that's if I knew what "A" quality meant. :-)
Other than that, not a bad effort for a dash project. It's a neat idea and something that could prove very useful.
Well I'd be more likely to use a piece of code if I see that people have constant commits that are raising the quality of the code base. At least this way you aren't just going by commits/releases, you get to see how they changed the quality of the product.
Number of lines of code? Size of methods? Number of commits? How much you like them?
An about page with the grading methodology should probably be the next thing you publish. Also, in my mind the historical breakdown is irrelevant. I couldn't care less if the project sucked two weeks ago if they re-factored and are now "a" quality. Of course, that's if I knew what "A" quality meant. :-)
Other than that, not a bad effort for a dash project. It's a neat idea and something that could prove very useful.