5 ms·
We talked about this at $WORK today, it's already on the board to be pulled out and replaced with an alternative. The guy's got a valid point, especially as ma
by csmattryder 3y ago
We talked about this at $WORK today, it's already on the board to be pulled out and replaced with an alternative.
The guy's got a valid point, especially as many Big Tech companies are using it, but this is a massively fucked up way to go about it. If you're going to do this, what else are you going to exfiltrate under the guise of open source sponsorship?
Pin to 4.18 until you've got a migration plan.
- hightrix 3y agoThis is the only possible response many of us are able to give to this issue. Trust has been completely destroyed. What if the next malware attempt isn’t discovered immediately? Anyone continuing to use Moq is opening their company up to possible litigation. Anyone know of a good drop in replacement? Internally we’ve gotten the ok for our next release to continue with this software pegged to a pre 4.20 release, but we’ve also been given the directive to “dump this guy” as soon as possible.
- brewmarche 3y agoThere’s NSubstitute. Haven’t used it personally but I’ve read good things about. I will have to look into at work as well since we’re also using Moq.
- shade 3y agoNSubstitute is good, I used it at a previous job. I've favored Moq in the past because I think there are a couple of things it makes a bit easier or is a bit less opinionated about, but NSub is perfectly cromulent as well. Someone posted a quick guide to migrating a bunch of it easily in one of the issues in the Moq repo discussing this whole mess: https://github.com/moq/moq/issues/1374#issuecomment-1671241122 https://github.com/moq/moq/issues/1374#issuecomment-16712411...