The random dep you grabbed that some hobbyist hammered out in a weekend... may not have 2FA on github, or maybe their email domain is about to expire, and it is very likely no one reviewed it.
If you choose to use the latter because it does what you need, then you are now the first party accepting the additional responsibilities of reviewing and maintaining that code to the level of safety appropriate for your use case.
If you are making a video game for personal use, then maybe the worst case scenario is tolerable for you to not care. If you are handling PII or money of other people... then suddenly you /must/ care.
An OS is backed by thousands of developers, and usually billions of dollars. Theres negligible risk that the momentum stops.
If that OSS library, that is fundamental to your business, has three developers, then maybe you do have a problem.
Linux is a massive C codebase one can never /fully/ trust or harden and high security applications with sufficient resources should favor formally verified microkernels like SeL4 whenever possible.
I think it can be done. But I think it needs industry-wide effort in a huge way.
Why stop at the standard library? What about the rest of the language toolchain? Compilers, interpreters. What about the OS?