License. What dependencies they bring with them and their license. Test coverage. Whether it has sufficient backing - i.e. from a larger company or very acti

License. What dependencies they bring with them and their license. Test coverage. Whether it has sufficient backing - i.e. from a larger company or very actively and independently developed. Definitely do not look for a possibility where we have to fork and maintain it ourselves. How does the "Issues" section look like. Who are other users. Where is the artefact hosted. Exposes APIs in a way that we can easily wrap it in our app and that the wrapper part doesn't have to be complex or has to be modified specifically for this lib. Has debugging and troubleshooting info/docs. If the doc is too big or too complex I would preferably not touch it. I prefer libs which expose very little and are documented simply in human readable ways.