Devs can add whatever they feel like on their workstations but it will be a sad build server if they get pushed without permission.
Devs can add whatever they feel like on their workstations but it will be a sad build server if they get pushed without permission.
Anything else will get abused in the name of expediency and just-this-one-time.
Also, the process for adding a crate/gem/module/library needs to be the same as anything else: license review, code review, subscription to the appropriate mailing list or other announce channel, and assignment of responsibility. All of these except code review can be really, really fast once you have the process going.
All problems are, at least in part, dependency chain management problems.
The dependency trees for most interpreted or source-distributed languages are ridiculous, and review of even a few of those seems practically impossible in a lot of development environments.
It's an obvious one, but distasteful to many people.
Would you care to state the obvious very clearly, for the dense ones among us?
Therefore, you must only use software for which the dependency trees are not ridiculous.
And that means giving up on software with ridiculous dependencies.
A compromised dev machine is also a problem.