I don’t really see how it’s NPM at fault here. This was caused by a malicious actor taking control of an account and putting out bad packages on it. It could happen on any package repository for any language
My understanding is that for most package managers the signing keys are held by a smallish number of maintainers responsible for entire sections, who presumably keep those accounts pretty tightly secured. Not impossible to take over, but it’s a smaller attack surface.
While for NPM as far as I know every uploader keeps their own account and there’s not even signing keys to lose control of.
I’m beginning to think this “NPM” thing isn’t a great idea.
Its always npm
I don’t really see how it’s NPM at fault here. This was caused by a malicious actor taking control of an account and putting out bad packages on it. It could happen on any package repository for any language
Trust by default for a atomic packaging system. Entirely NPM’s fault.
My understanding is that for most package managers the signing keys are held by a smallish number of maintainers responsible for entire sections, who presumably keep those accounts pretty tightly secured. Not impossible to take over, but it’s a smaller attack surface.
While for NPM as far as I know every uploader keeps their own account and there’s not even signing keys to lose control of.
I’m not familiar with npm but why is this always NPM? Is it a specific issue they have?
It’s a “package manager” that has zero integrity checks built in. Web devs also love it. Nice combination.
Culture problem imo.