3 ms·
Committed 23 days ago and no contributor or author has deigned to do anything about it. Says a lot about the health of this library. The "open source maintaine
by sph 5y ago
Committed 23 days ago and no contributor or author has deigned to do anything about it. Says a lot about the health of this library.
The "open source maintainers are not your bitch" argument is moot when one publishes a library on something like npm and then disappears when a security incident happens. I reckon publishing a library on a package manager should come with a promise of responsibility or at least communication.
- emteycz 5y agoI don't think that's reasonable. People use NPM for various purposes, and professional-grade software with guarantees is only one use of many. You need to vet your packages. Always, even if you paid for it. There are package managers that work with Github repos. Should this apply to every public Github repo too?
- sph 5y agoFine, then let's adopt a standard of announcing whether you're serious about your projects, and then other people know if they can rely on your library or not. Some kind of "verbal" promise of being proactive when catastrophe happens. That you'll personally won't bundle malware in your code, or your reputation will suffer. I mean it. The open source world, especially the JS ecosystem, desperately needs something like this. And a monetary incentive isn't enough, unless it's significant, but no one will pay $500 a month per JS library they depend on. A simple ".serious-project" committed to the project root would suffice.
- yellowapple 5y ago> And a monetary incentive isn't enough, unless it's significant, but no one will pay $500 a month per JS library they depend on. Maybe they should, and if they fail to do so, then maybe they have zero right to complain about it.
- sph 5y agoLet's see how many people will pay money for their `is-odd` dependency. Again, enforcing responsibility by paying is non viable and doesn't scale, especially in the JS world when you depend on 500 packages for a bare React project. Yet I as an open source developer I want to announce that my projects are actively maintained, i.e. I'm serious about them and I'll react in less than 23 days if someone adds malware to my code.
- yellowapple 5y ago> Let's see how many people will pay money for their `is-odd` dependency. If they're unwilling to pay for it, then maybe they should reconsider including it as a dependency? And maybe, just maybe, if they include it as a dependency without any intention of paying for it, then they should have zero expectation of support for it? And likewise... > especially in the JS world when you depend on 500 packages for a bare React project ...then maybe they should consider an ecosystem wherein they, you know, don't depend on 500 packages for a bare project? And if they do, then maybe - just maybe - they should expect to either contribute to the ongoing maintenance of those 500 packages or else be entirely unsurprised when they inevitably fall into disrepair? > Yet I as an open source developer I want to announce that my projects are actively maintained Then do so: remove the clauses in your licenses w.r.t. warranties and liabilities and fitnesses for particular purposes, and declare that you'll commit to active maintenance. If that's your prerogative, then nobody's stopping you. Chances are, though, you'll grow weary of the expectations from others with which you've burdened yourself without compensation. A better form of seriousness would be to offer support to those willing to pay you for it. Naturally, this means producing something that's worth such an agreement.
- ElectricalUnion 5y ago> Fine, then let's adopt a standard of announcing whether you're serious about your projects I don't believe in Tidelift myself nor I actually pay them any money, but there's that already. If you're willing to use less recent packets, you can trust vendors like SUSE or Red Hat to do that for you.
- deleted 5y ago[deleted]
- MaxLeiter 5y agoI disagree, the responsibility is ultimately on the consumer, assuming the dependency is FOSS.
- patrickaljord 5y agoIf it's a bug, sure, but intent matters. If it is malicious code written to harm people on purpose, than the responsibility is on the FOSS dev. What if it is code that is used to interact with hardware and that there is malicious code intended specifically to physically harm the user? Is it ok to kill someone if it's through FOSS? I don't think so.
- amscanne 5y agoIs this a security incident? My first read was that it was just pushed by the maintainer directly (“Viktor”). I thought the headline was misleading. Is there any confirmation either way?
- sph 5y agoI don't think it is, the name seems to be spoofed and the email attached to the commit doesn't match @Yaffle. Git author and email are easily forged anyway.
- amscanne 5y agoIs it even spoofed, or is that his real name? It could just be an email not publicly associated with the GitHub account. AFAIK GitHub displays links to profiles purely as a convenience, based on the commit metadata.
- pid-1 5y agonpm is not a curated repository of high quality packages. Folks using it like so are at fault for having no digillence.