copyright software liability france
Working on code with uncertain licensing at another company&#39;s behest
<p>so the situation I want to ask you about is as follows:</p>

<p>The Client Company has a project that is made of three parts:</p>

<ul>
<li>A front-end web app</li>
<li>A back-office</li>
<li>An API (back-end)</li>
</ul>

<p>The front/back parts were developed by a contracted company, we can call them Bad Contractor, and the API was developed by a few contracted IT students.
The result for the Client is a late, non-functional, mess of spaghetti code with severe security problems.</p>

<p>This is where we come in: Client wants us to quickly hack a few fixes/functionalities on the existing codebase, the bare minimum that they could continue working with, after which we will redo their project cleanly from scratch.</p>

<p>The front/back parts have NO license mentions, the API part has a license mention that specifies that the code belongs to the authors until Client has paid the authors in full - which has been done, so there shouldn't be an issue with that part of the codebase.</p>

<p>All the fees for Bad Contractor were paid in full as well - however their relationship ended on bad terms because of the quality of their work (they wanted to keep 'maintaining' their mess), and to our knowledge, the source code probably still belongs to them (in France, AFAIK, if there is no explicit mention of giving away source code, a license is only for use).</p>

<p>So my questions are: who is liable if Bad Contractor learns of this reuse of their code? Is our Client liable for giving us the code and telling us to work on it? Are we liable for accepting to work on code the client gave us? Or both?</p>

<p>Heck, can <em>I</em> be made personally liable if it can be proven that I worked on it with this knowledge, even just as an employee?</p>

<p>If Client was foolish enough to pay Bad Contractor (BC) without obtaining a proper assignment of copyright in the source, or at least a sufficient license to allow Client to use the code and create modified versions, then BC owns the copyright to the source, and anyone who <strong>creates</strong> a modified version without permission from BC is a copyright infringer. The contract under which BC was hired <strong>should</strong> spell out what rights Client is to acquire, and when they will pass to client's ownership, but it might be that Client didn't get such terms into the contract. Or perhaps BC disputes that Client has fulfilled all its obligations.</p>

<p>Yes, an infringement claim could be brought against an individual employee, although it is more likely that it would be brought against the employer, or against Client. It could be brought jointly against all three: programmer, new contractor (NC), and Client. </p>

<p>Of course, BC's IP rights only matter if BC files an infringement suit. And it might be that a court would find an implied contract, in line with industry practice and the fees that BC was paid, and toss out such a suit. But courts are often reluctant to create contracts that the parties never agreed to. It would be risky for NC to depend on such an outcome of a possible suit.</p>

<p>If you or NC are to work on this, you might want to have a contract in which Client explicitly indemnifies you for any copyright claims by BC, saying that they will take on and pay for the defense of any copyright suit BC  may bring, and pay any damages that may be awarded to BC. That would largely remove the risk for NC and for NC's employees.</p>
