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.
[ Parent
| on HN ]
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?