The library point is especially instructive IMO. Copilot introducing "learned" security issues, for example, is a problem separate from the copyright risk. Cu

The library point is especially instructive IMO. Copilot introducing "learned" security issues, for example, is a problem separate from the copyright risk. Currently, it's often a matter of updating a dependency to patch things away. How do you do that when you barely understand the code it helpfully generated for you? People will jump to say "well that's using it wrong" but the reality is if you allow this in your org people will use it this way.