Thanks to the proliferation of open source code, there are more options than ever for developing applications. Keeping track of the potential licensing issues associated with all the dependencies that exist in that software is a whole other matter.
Software licenses are often the bane of application development in the enterprise. Developers tend to get excited about one module or another without checking on which actual rights the organization might have to the software. In far too many cases, there are not only financial implications, but any and all modifications made to that software can become the property of an open source project or the commercial entity that created the original module.
With the rise of open source and repositories such as npm and Github, the way applications are constructed, deployed and managed has been utterly transformed. But for all the productivity those tools have helped advanced, the fact remains that navigating licensing terms and conditions is a dark art. Understanding the implications of those terms and conditions before any additional code is written can easily be the difference between creating the next big thing in the enterprise and a legal quagmire that everyone involved comes to deeply regret.