Today’s software is built like a Lego model. Instead of a singularly developed string of code, multiple building blocks of existing code are used to create a codebase. Some of those building blocks are developed in-house by the software vendor. Others are developed by third-party commercial software providers. And a lot of them come from open-source projects. When you’re a company that puts that codebase into your final product, you must take precautions to minimize the risks that each type of code presents to you and to your customers. This is what is meant by protecting your software supply chain. It’s also how you maximize the value of the code for you and your customers. Each type of code has its own set of benefits and risks that need to be understood and managed. This article addresses just one type of those building blocks: open source software (OSS).
Recent Posts
- Stewart Grants Discretionary Denial Due to Patent Being Dismissed From Litigation
- U.S. Government’s Intervention in Patent Case Signals Good News for Patent Owners Seeking Injunctions
- Gaming Patent Litigation on Both Sides of the ‘v’ | IPWatchdog Unleashed
- Recentive Rehearing Petition Challenges CAFC’s Broad Section 101 Exclusion of Machine Learning Inventions
- Other Barks & Bites for Friday, June 20: Advocate General Tells CJEU to Affirm €4 Billion Antitrust Fine Against Google; Recentive Challenges Section 101 Invalidation of Machine Learning Claims