Where is the issue ? When in inspect a library; - I can see the number of downloads on the npm website and so on. - I can see the issues and pull requests on

Where is the issue ? When in inspect a library; - I can see the number of downloads on the npm website and so on. - I can see the issues and pull requests on github - I can do a git clone + npm test to see if the tests still run or even better see the travis batch that is in the readme. I prefer a vibrant community and lots of libraries over a slow and "solid" library development community. In the end - I need to write code any way to fix any of the libraries issues... With lots of libraries, at least I have the chance that somebody already forked the library and fixed my problem. Otherwise, I ll fork the lib - fix the issue and use the fork myself and send a pull request to the original lib. Once the pull request is accepted - i can just point my dependencies again at the original lib. Perfect isn't it ? I fix the problem for myself and the community gets a fix back to the original lib almost for free. So yes, there is garbage out there, but I feel I have a lot of tools to "smell" it and stay away of these before investing too much time.