If you are a buyer of coding services, why should open source in the Deliverables concern you and what can you do to protect yourself?
Open source code in your deliverables can be a major problem. It may open you up to potential intellectual property infringement actions or, during due diligence, it may torpedo an acquisition.
So, what do you do in your consulting agreements?
First, request a warranty stating that there is no open source in the Deliverables. More specifically, I like to say that there is no code that is governed by viral license agreements.
Second, I do not distinguish open source contained in the Deliverables from the Deliverables themselves. When I ask for warranties and indemnification, they apply to “Deliverables” and everything included in those Deliverables. That way, the consultant is on the hook for the entire Deliverable.
If the consultant is unwilling to provide the warranty and/or the indemnification, then I require that any open source must be preapproved in writing before being included in a Deliverable. Absent your written approval, the source code is treated as part of the Deliverable and, therefore, not excluded from the warranty or indemnity under any circumstances. If open source is included in the Deliverables, make sure that you also get a copy of the applicable open source license.
Recent Comments