I think in this text, details like the timeline are simplified a bit too much. But I agree with the general tendency described.
There was never a time where software was perfect, but the accelerating cadence of serious, widespread incidents with real-world effects seems real.


Which by the way also leads to an interesting state of matter once you reach the point where every dependency problem you fix causes on average more than one new problem elsewhere. The reason is that if dependencies are not strictly backwards-compatible, that’s a breaking change – and with large depedency graphs, breaking changes tend to cause more breaking changes. You get kind of a nuclear chain reaction.
Which is the reason you lock down the dependencies and maybe you build a in-house server to host them (be NPM, composer of whatever) so everyone fetch a certified version and it is the same for everyone on every project, with an upgrade that need to follow a strict process.