Improving quality of submitted hacks (code)

[Hornstar]

I'd like to hear what others think could be done to improve the quality of submitted hacks here.

A couple weeks back on vb.com in the licensed area people were discussing areas about the quality of code in some of the hacks submitted on vb.org and how they can severely affect big boards etc.

-----------
One idea I had was that there could be a team set up to approve hacks before they are shown. Exactly the same way the articles forum is set up: https://vborg.vbsupport.ru/forumdisplay.php?f=184
This way will ensure hacks that are submitted are safer for our sites. Currently anyone could submit a hack where it could potentially delete/screwup our whole database.
It could also give the chance for this 'team' to give feedback and suggestions to the coder before the hack are approved. Kind of like one final pre beta test.

What other things do you think could be done to improve this area on vb.org?