I disagree, the current system is just too inflexible and static. To give an idea, lets look at Module::Build. The rating system gives a 3 star. However, the ratings apply to the module over the course of 3+ years which has had many changes.

If someone complains about a bug from 3 years ago is that rating properly reflective of the utility of the current module? I don't think so.

On the other hand, should we reset the ratings for a particular module everytime they release a new version? I don't that either.

I would rather see a way of inventorying of modules that get used in scripts or modules that using cpan modules, but they, themselves are not on cpan. It would give an idea of which modules are actually being used by developers. It would not be perfect, but seeing what people are actually using would be incredibly useful.