Every single library that is included in your code is a backwards compatibility liability. Every single such library is a maintenance obligation. Every time those who run that library's project decide to do something major, you have to jump through hoops to ensure compatibility of your code with the new version. Each of them become a liability.

Only the libraries which are stable for long duration, those who have long term releases, or better, libraries and software whose project owners know the importance of backwards compatibility and see it as a fundamental concept that protects their community.

Such libraries, frameworks can be used with confidence and most of us are using it. Its the 'flavor of the month' types, or projects which do not care about what they may break with their next release and therefore dump all the burden of backwards compatibility on the users of their libraries and frameworks which are the problem.