Putting aside the long-term concerns such as building skills, maintainability, team dynamics and so on, there's a simple effort-based cost-benefit analysis you

Putting aside the long-term concerns such as building skills, maintainability, team dynamics and so on, there's a simple effort-based cost-benefit analysis you can do. To responsibly use a bit of software Not Invented Here, you have to (a) understand what it does (b) research the available alternatives (c) check that you're happy with its dependencies (d) deal with any licensing issues (e) check for known issues and bugs (f) if possible, take it for a test run which is likely to be a nontrivial amount of work. If it's less effort to just write it, you may be better off just writing it.