Too bad that we don't have test cases for each packages. If that would be the case you could automatically set or reset the maturity level depending on the number of cases that run successfully.
Another option would be to include bug tracker in the process so that the number of open bugs influence the maturity level as well.
The danger I see with the proposed maturity level standard is that it lacks of some automation. This will results packages to reach a high level during their life cycle and stay at a high level even if the code base get's messed up over the time.
Therefore I would suggest that the level is set involving the testing results and the bugs in bug tracker.
