Regulation would have to start with simple coding standards. Updated yearly. Much like building codes. A project could pick what standards they wanted to adh

Regulation would have to start with simple coding standards. Updated yearly. Much like building codes. A project could pick what standards they wanted to adhere to, and then everyone on the project would have to adhere to those standards -- the whole project would be audited by a third-party after the fact for compliance. There are plenty of good, short, concise coding standards to draw from. Especially useful in giving non-technical people the confidence that things were built consistently... if not correctly even. This is about as simple as it gets: * WordPress Coding Standards – Make WordPress Core || https://make.wordpress.org/core/handbook/best-practices/coding-standards/ https://make.wordpress.org/core/handbook/best-practices/codi... I'm sure there are others that aren't terrible. I do think having more standards would help, standards defined by the devs on the project. If they get to choose their benchmark, then it's just about consistency of approach. Not a bad thing, right? Currently it's the wild west, and the only thing a dev can do is say, "It's my word against theirs, their code is bad."