114
Software is breaking down at a systemic level, by Jimmy Breck-McKye
(www.breck-mckye.com)
This is a most excellent place for technology news and articles.
This guy is delightfully close to a cause, but not really.
In the enterprise space, we largely avoid NPM or Composer, et al, because those very best-practice docs (iso27002, here, later SLSA) prohibit repos that obscure or frustrate validation and code pedigree; and the gleeful incestuous inclusion of projects within projects means source code isn't properly managed - a failure - so npm won't do. SBoM and validation is key.
So that covers half his premise; and while some shops or people use and love npm and cpan et al, the kind of people maintaining banking or travel systems should most absofuckinglutely NOT be using those ecosystems lest they lose their certification the first time a clued audit comes through. You wouldn't accept code violations from your architect or your builders, and programmers are the same way in that space.
The problem, it seems, is sloppy people doing sloppy things and not getting caught.
I'm sure Ai is a big help with this, but it's only enabled by the same sloppiness that was already present.
Great news: civil courtrooms try negligence and code-violation cases all the time.
Yes, unfortunately the SBoM too often is a Yaml file that gets changed every time someone wants to use a new Ruby gem. https://openssf.org/projects/slsa/ is a page with a small blurb and an embedded video! slsa.dev looks interesting and I'll check into it later.
Management everywhere cares about velocity more than they care about anything else. They'll always find workarounds for anything requiring careful thought.