What happened to two libraries that had more than 20 million downloads and thousands of dependent projects after a developer corrupted them?
In response to the corrupted libraries, Microsoft quickly suspended his GitHub access and reverted the projects on npm. The developer's rights to do what they want with their code, no matter how many projects they have, were the subject of a debate.
"GitHub suspending someone's account for modifying their own code in a project they own however they want to scare me a lot more than NPM reverting a package," said one company's Director of Engineering & Technology. I like what Marak did to make a point.
_
An article on iProgrammer outlines a dilemma that might seem clear-cut. "Yes, it is open source in that you can fork it and contribute to it, but does this mean that you can't change or even destroy your own code?"
The developer's account is active, he has been allowed to remove his faker.js library, and it would appear that the whole affair is just for intellectual debate.
_
All Rights Reserved © 2024
