> raw package count gets to be an extremely poor indicator of quality after a certain level has been reached. Broadly speaking I think the best indicators are

> raw package count gets to be an extremely poor indicator of quality after a certain level has been reached. Broadly speaking I think the best indicators are always going to be domain specific -- which set of packages is most used within the context of what you're doing? A million awesome packages for Excel automation aren't much help, per se, for huge file chunking or BigData work. From that point of view it's more relevant to look at the size of the successful projects in that market that resemble your technical goals.