If you're working for a company, then
you should probably let the lawyers of your company decide what is acceptable and what isn't. You can get into a lot of trouble if you, as a lay person who doesn't really understand the details of the law, decide to use some library in the product that your company sells, when somebody later discovers that you are breaking the license in some way. Your company might get sued. This is especially true if you are going to make a software product that you are going to sell (i.e. some piece of software that you are selling to customers).
Some licenses let you do almost anything, and some require you to make your source code and the source code of the libraries you are using available (such as the GPL). (Note that I am also not an expert on this - I'm not responsible if you make decisions based on what I say about this).
On almost any product that I've worked on, for many different companies, I've used many open source libraries and tools. Almost all of that software was custom software, specifically written for the specific client, who gets the rights and responsibilities over the source code and software that I wrote.
So, it isn't as simple as making a list here. You have to carefully read each license and if you have any doubts consult a lawyer that can explain you exactly what your rights and responsibilities are according to the license, for your particular goal.