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).
Copyright
- Computer Law
- Fair Use
- First Sale Doctrine
- Copyright Office Makes AI Authorship Policy Official
- Copyright Claims Board Finds for Photographer on Infringement But Curbs Damages in First Final Decision
- Recognizing AI-Assisted Art: The Copyright Office is Using the Wrong Legal Standard
- We Need a Copyright Reboot for Robots
- StarrAI Night: AI Art and the Necessary Changes in the Copyright Law
Recent Posts
- Bayh-Dole Opponents Slam-Dunked Once Again
- SCOTUS Skeptical that Bad Spaniels is Parody, But Questions Need to Overturn Rogers
- Justices Seek Abitron Parties’ Help in Articulating Bounds of Extraterritorial Application of Lanham Act
- U.S. Taxpayers Should Not Be Paying for Private Patent Infringement
- UK Court Hands Down Key FRAND Ruling in InterDigital v. Lenovo