5 ms·
I can tell a lot about a dev by the fact that they single out npm/js for this supply chain issue.
by zachrip 1y ago
I can tell a lot about a dev by the fact that they single out npm/js for this supply chain issue.
- deleted 1y ago[deleted]
- hsbauauvhabzb 1y agoThat they’ve coded in more than one language?
- brobdingnagians 1y agoLots of languages ecosystems have this problem, but it is especially prominent in JS and lies on a spectrum. For comparison, in the C/C++ ecosystem it is prominent to have libraries advertising that they have zero dependencies and header only or one common major library like Boost.
- RUnconcerned 1y agoWhat other language ecosystems have had this happen systematically? This isn't even the first time this month!
- blueflow 1y agoPython/PyPi.
- johnisgood 1y agoRust.
- LPisGood 1y agoGo has this issue
- SkyPuncher 1y agoNPM is the most popular, so it happens the most frequently. All of the other ecosystems are just as susceptible. Unix had a big scare last year because of XZ Utils. https://en.wikipedia.org/wiki/XZ_Utils_backdoor https://en.wikipedia.org/wiki/XZ_Utils_backdoor
- Sankozi 1y agoNo they are not as susceptible - auto updating dependencies, post install scripts and culture of thousands of crappy micro packages (like left-pad) is mainly a NPM issue.
- zachrip 1y agoPackages are not auto updated if you have a package-lock. Agreed that post-install, left-pad, etc have been overall problematic tho.
- mdavidn 1y agoRubyGems is susceptible too.
- lithos 1y agoJust more engineering leaning than you. Actual engineers have to analyze their supply chains, and so makes sense they would be baffled by NPM dependency trees that utterly normal projects grow into in the JavaScript ecosystem.
- zachrip 1y agoDo you think companies using node don't analyze supply chains? That's nonsense. Have you cargo installed a rust app recently? This isn't just a js issue. This needs to be solved across the industry and npm frankly has done a horrible job at it. We let people with billions of downloads a month with recently changed password/2fa publish packages? Why don't we pool assets as a collective to scan newly published packages before they're allowed to be installed? These types of things really should exist across all package registries (and my really hot take is that we probably don't need a registry for every language, either!).
- LaGrange 1y ago> Do you think companies using node don't analyze supply chains? I _know_ many don’t. In fact suggesting doing it is a good way to be looked at like a crazy person and be told something like “this is a yes place not a no place.”
- pclmulqdq 1y agoIt is solved across the industry for those who care. If you use cargo, npm, or a python package manager, you may have a service that handles static versioning of dependencies for security purposes. If you don't, you aren't generally working in a language that encourages so much package use.
- keyle 1y ago2FA would certainly help, however you'd still have malware like these silently updating code and waiting for the next release. We'd have to rely on the developer to notice, and check every line of code they ship, which might be the norm but certainly not 100% of cases.
- 1y ago
- Aeolun 1y agoI think it’s just that a lot of old men don’t like how popular it has become with script kiddies.
- cedws 1y agoThe JavaScript ecosystem has a major case of import-everything disease that acts as a catalyst for supply chain attacks. left-pad as one example of many.