@ayo @bert_hubert Reminds me of the questions I have when I choose dependencies:
① Are other people using it? (easy to check via distros like Alpine or Gentoo)
② Could I end up maintaining it? (either due to upstream passing me maintenance, or needing to fork/patch it)

Question ① isn't very important but makes sense to check, could otherwise end up missing a better dependency without doing so, and sometimes turns out the dependency is used by no one because it's unusable.
Question ② is probably the most important, could skip it for throwaway scripts but well… temporary sometimes spans for a very long time.

Note: I tend to consider not just libraries but also utilities, buildsystems, language implementations as part of the dependencies. Could even consider deployment like packaging into distros in there as well but can't really call that a dependency of the software.