There's a program called rsync that's used to backup files between locations. If you use Linux you probably know about it. It's not something you use as like its own program exactly, it's more like an automated process that you set up to run in the background in various ways.
A few days ago some people started noticing that rsync was suddenly failing in unexpected ways. When they went to the project hub to find out why, they discovered that the sole maintainer, "tridge", has started vibe-coding it. He didn't catch the new bugs because he also converted his test suite (poorly, evidently) from bash to Python (also presumably using the chatbot to some degree) and the new versions of the tools were bad.
People started spreading this information and a lot of them decided rsync couldn't be trusted anymore and they've started to either rollback and freeze to the pre-vibe version or have started exploring the OpenRsync fork as an alternative.
Tridge fought back with an open letter in which he claims to be the unfair victim of an anti-AI lynch mob, and a couple of Linux youtubers have made videos defending him as such, tending to spin the event as a few people going irrationally cancel-crazy after just happening to find out that the perfectly-fine rsync was being vibe-coded and leaving out that the only reason anybody found out to begin with was because rsync was
breaking their scripts and losing their data.