User blog comment:Rappy 4187/Tools For Making JavaScript Review Even Easier/@comment-29457887-20160717104424/@comment-24473195-20160717180117

While I agree that a fully automated system is something best left to researchers rather than Mediawiki engineers, some degree of automation is indeed possible. For very simple examples, it is trivial to detect changes that make no difference, and automatically approve those. Things such as whitespace changes, changes to comments, changes to escaped i18n strings in a separate file / page, and so forth. In fact, there is an existing library for i18n in mediawiki, but that requires an extra ajax call.

So there is still room for improvements even without full automation. Another idea would be to deploy simple automatic static analysis tools that either warn about code or reject it if it has security  issues (https://www.owasp.org/index.php/Source_Code_Analysis_Tools).