Before revision: These risks can be organized into 5 categories: OSS Version Control: risks of changes introduced by new versions Security: risks of vulnerabilities in components - Common Vulnerabilities & Exposures (or CVEs) License: risks of Intellectual property (IP) legal requirements Development: risks of compatibility between existing codebase and open-source software Support: risk of poor documentation and Obsolete software components Shortly after the foundation of the Open Source Initiative in February 1998, the risks associated with OSS were raised and organizations tried to managed this using spreadsheets and documents to track all the open source components used by their developers.
After revision: These risks can be organized into 5 categories: OSS Version Control: risks of changes introduced by new versions Security: risks of vulnerabilities in components - Common Vulnerabilities & Exposures (or CVEs) License: risks of Intellectual property (IP) legal requirements Development: risks of compatibility between existing codebase and open-source software Support: risk of poor documentation and Obsolete software components Shortly after the foundation of the Open Source Initiative in February 1998, the risks associated with OSS were raised and organizations tried to manage this using spreadsheets and documents to track all the open source components used by their developers.