But it gets worse. Often the people promoting the software aren't the people who wrote it, and they may make claims that the authors never intended.
None of these things mean that the authors accept formal liability, but morally speaking, if you're encouraging people to use your software and you're participating in an ecosystem promoting its usage, and it turns out to have bad security flaws, then maybe you shouldn't be so encouraging? Be upfront that it's just something you threw together. Add a few speedbumps. Maybe don't publish it on npm? Disrupt the hype train.
Disclaiming all responsibility should imply that you also don't hype it up and set people up for failure.