That's the usual "open source" wasteland really - code gets piled on top of code and it's about as "open" as the sand is - go sift it all to find the gems, they are totally in the open. The only way to actually escape this sort of "open" is to acknowledge that lines of code are a liability not an asset (the more, the worst) and then to have actual ownership (as in: responsibility) of code - pretty much what V together with the WoT does really.
With a plugin architecture there's no real way to gain control of the wasteland. This is created by third-party vendors. It'd be like Microsoft trying to reign in the loads of garbage produced for their platform -- which even failed when they opened a store. Thus a controlled pluging marketplace would also not likely fix the issue.
Not sure what you have in mind re controlled plugin market place but hat wasn't my idea at all, no. Taking control of the (any) code that one uses, indeed. But that doesn't mean trying to/being concerned about what rubbish someone else might add. The point with V is simply that "adding" by itself doesn't do anything really - it matters who does it and it matters in a very personal manner aka to what extent and in what way you (the user) trust them (or not). Basically the view that you have on some software or another depends on the people you trust (and that's your choice, of course). In turn, it's really the network of people reading the code and signing it (or not) that matters most, not just the code itself nor some central controlling authority. The point is that the one running the code on their machine should have control as to what code they run, NOT that "Microsoft" (replace with any code-producer you want) should have or even attempt to have control, that's about it.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.