VMoodle

Yes there is a bug for making an event in config.php @ MDL-34632

In this particular case there is absolutely NO WAY do resolve the configuration hook when any moodle script starts. Actually, the VMoodle block is more likely a "local" plugin affecting a global behaviour of Moodle, but was setup as a block for convenience of architecture in 1.9. This would be an overheading work to change architecture now, as the hooking in config has been reduced to the minimum footprint possible.
Remind the config.php is included at very early stage of the page construction (quite the early beginning) and that all what follows in script will depend on the choice of the effective database (including the choice of plugin itself).
Cheers - Valery

The readme file indicates that the main config.php file needs to be changed to include the vmoodle/vconfig.php file. As a result, it is not truly a block. Is there a way of providing a hook to pull in includes from plugins into config.php? Would that be desirable? In any case, until zip file validates and we have some clarity on this I am going to mark this as needing more work. Peace - Anthony

Note $plugin-maturity var is in the version.php but recurrent miparsing of the contribution analyser
Tells it not there even when it is...
Actually maturity value was not good...

Thanks for sharing this!
ps: there is an extra readme file. also you may want to add $plugin->maturity to your version.php