Allow blocking / denying by library name
Problem to solve
An organization may wish to prevent use of specific libraries, not just licenses, in their code. The developer should be promptly informed when adding the library that it is prohibited by policy, and any merges should be prevented.
Intended users
Further details
If the code is available to be leveraged, allow this to be set at group and project level. At group level allow it to be default, or forced on (can not be turned off). If this is not yet code that can be leveraged, break this into another issue.
Proposal
Permissions and Security
Documentation
Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Links / references
Edited by Nicole Schwartz