Coping with Loss (in Open Source)
Many software development teams use external components in their projects, libraries, or tools provided by commercial vendors or open source communities. However, as anyone who has ever had to scramble after a vendor has gone out of business can tell you, these external dependencies are not without risk. Software companies can fail, products can be discontinued and open source projects can stagnate. Components that aren’t being maintained or security risks that aren’t being addressed can put your project in a difficult situation.
With commercial components, you may not have much control over the decisions vendors make or even whether they stay in business. However, in the case of open source (OS) components, you can mitigate these risks and keep your project’s dependencies from creating more problems than it solves.