What you’re describing does exist, it’s integration and end-to-end testing. It requires no input from the library developers and will always be safe from their

What you’re describing does exist, it’s integration and end-to-end testing. It requires no input from the library developers and will always be safe from their mistakes. SemVer is a simple no frills tool to provide meaningful information in version numbers, but it is not a replacement for proper testing. If SemVer misleading you is that big a deal to your projects, you would already have that testing in place, making any SemVer violations a non-issue for your project. But in that case SemVer would still be useful because when making any minor-version package updates, you would be able to expect that all your tests would continue to pass, versus upgrading a package to a new major version, where you’d definitely expect to have to refactor.