> Added their own package repository (MRAN), replacing CRAN.
How is any of this different than the many incompatible Linux packaging solutions?
How would you address insecurity and trust relations if you weren't a first-class contributor of CRAN? (consider the recent Python package exploit; although amateur, it's still an indication of such issues; I'm sure I remember this was an issue with the Perl packages as well; wasn't there an exploit pushed to the Linux kernel tree at some point years ago?)
The narrative changes from "MS is EEE'ing CRAN" to "MS allowed a package with exploits to be deployed from CRAN".
I am not familiar with any of the issues within the R ecospace, but I am very familiar with corporate culture, security, and liability awareness.