As a developer running a company using an open source library my primary concern is, will this technology choice serve my project’s needs? Happy to contribute

As a developer running a company using an open source library my primary concern is, will this technology choice serve my project’s needs? Happy to contribute to help but knowing that the persons who actually understand and took the responsibility to maintain a library are around, informs my choices. It’s fine if you don’t want to fix problems in your library anymore, that’s your choice, I just won’t use that library—but I need to know what’s going on or else I can’t make choices for my own benefit. Whether you like it or not, posting an open-source library is equivalent in my and many developers minds, to telling other people that they ought to use your code in some way. If the way you signal them to use it is as a dependency in their own critical software, by posting it to a package manager and hyping up the benefits of your design choices and code, I do think it’s kinda on you if people get burned by deciding to work with you, even if indirectly. Communication is the point - if you don’t want people to expect maintenance of your software, say that you won’t maintain it, don’t put it on a package manager, or else people will get the wrong idea, because open sourcing and posting the code is also communicating something, even if in your case it’s unconscious and not what you actually meant.