Re:Bitwarden CLI Compromised in Ongoing Checkmarx Supply Cha...
by MetaWhirledPeas on Thursday April 23, 2026 @05:01PM
(#47881916)
Other package managers are magically immune?
[ Parent
| on HN ]
Re:Bitwarden CLI Compromised in Ongoing Checkmarx Supply Cha...
by c2h5oh on Thursday April 23, 2026 @05:06PM
(#47881992)
They are not, but npm is uniquely bad in that regard. Refusal to implement security features that would have made attacks like this harder really doesn't help https://github.com/node-forward/discussions/issues/29
Re:Bitwarden CLI Compromised in Ongoing Checkmarx Supply Cha...
by nirvdrum on Thursday April 23, 2026 @06:19PM
(#47882906)
The lack of a comprehensive standard library for JavaScript also results in projects pulling many more third party dependencies than you would with most other modern environments. It’s just a bigger attack surface. And if you can compromise a module used for basic functionality that you’d get out of the box elsewhere, the blast radius will be enormous.
Re:Bitwarden CLI Compromised in Ongoing Checkmarx Supply Cha...
by pico303 on Thursday April 23, 2026 @10:54PM
(#47884926)
Not to mention a culture of basically one-line packages ad infinitum. I downloaded a JS tool the other day to generate test reports and it had around 300 dependencies.
Needless to say I’m running all my JS tools in a Docker container these days.
Re:Bitwarden CLI Compromised in Ongoing Checkmarx Supply Cha...
by wombatpm on Thursday April 23, 2026 @10:56PM
(#47884938)
So why hasn’t someone created a batteries include JS library? I don’t program in JS on the backend so I don’t know how feasible something like that is.
Re:Bitwarden CLI Compromised in Ongoing Checkmarx Supply Cha...
by girvo on Thursday April 23, 2026 @11:07PM
(#47885010)
Everyone’s ideas of what batteries should be included differ
Re:Bitwarden CLI Compromised in Ongoing Checkmarx Supply Cha...
by wolfi1 on Friday April 24, 2026 @12:26AM
(#47885505)
I, for one, root for AAA
Re:Bitwarden CLI Compromised in Ongoing Checkmarx Supply Cha...
by hfsh on Friday April 24, 2026 @03:04PM
(#47894480)
*cries in ghettoblaster and Maglite D cells*
Re:Bitwarden CLI Compromised in Ongoing Checkmarx Supply Cha...
by stevekemp on Friday April 24, 2026 @01:58AM
(#47886147)
https://github.com/stdlib-js/stdlib was is one of several attempts at that, but yes the issue is that different people have very different views of what should be standard.
Re:Bitwarden CLI Compromised in Ongoing Checkmarx Supply Cha...
by fc417fc802 on Friday April 24, 2026 @07:59AM
(#47889038)
That doesn't seem like it should be an issue in practice? Rather than a single standard library endorsed by the language stewards if the community at large converges on a small handful of "standard" solutions that seems like it would satisfy the security aspect of things.
Re:Bitwarden CLI Compromised in Ongoing Checkmarx Supply Cha...
by erikerikson on Friday April 24, 2026 @10:29AM
(#47890802)
Lodash but also, which batteries?
Re:Bitwarden CLI Compromised in Ongoing Checkmarx Supply Cha...
by mayama on Thursday April 23, 2026 @09:26PM
(#47884433)
You could write most of the cli tools using stdlib in python and go, without need for including hundreds of libraries even for trivial things.
Re:Bitwarden CLI Compromised in Ongoing Checkmarx Supply Cha...
by NamlchakKhandro on Friday April 24, 2026 @12:26AM
(#47885504)
yes obviously.
isn't it obvious?
it should be obvious.
why isn't obvious?