A developer of some Ruby Gems pulled the code as a statement against certain entities (Department of Homeland Security — DHS) ultimately using the code. Chef gets owned in the process.
ZDNet has a good rundown of the incident:
https://www.zdnet.com/article/developer-takes-down-ruby-library-after-he-finds-out-ice-was-using-it/
It seems that developers at chef may have used an old copy of the dev's code to get things back up and running again, which seems like exactly the wrong approach.
(Score: 2) by HiThere on Sunday September 22 2019, @08:14PM
Well, it's none of your business as long as you didn't foresee the abusive uses, or design it to enable the abusive uses, or continue to maintain it despite the abusive uses.
If you do any of those things, you need to balance the good vs. the bad, and decide whether it is proper to allow use to continue (if you control that) or to maintain it (if you do that).
If you release software you've pretty much got to accept that people will use it as they choose, because you can't stop them. Not unless you've got fancier lawyers than they do, or have judges in your pocket...and even then not until you can show that they are using it in ways that you didn't approve of. So you might as well say "I place no restrictions upon use", because only the honorable will attend to those restrictions anyway. I believe that MSWindows has been used to control nuclear reactors despite explicit prohibitions.
Javascript is what you use to allow unknown third parties to run software you have no idea about on your computer.