Does a license found in a repository automatically apply to the code in the repository?
<p>Imagine this situation, you create a new project which is not intended to be  Open-Source, but you use a permissive framework which allows not opening the source code of your own project which depends on said framework.</p>

<p>Some time go by and you develop your application with version control, but then in your project structure you notice a LICENSE file with a copyright statement:</p>

<pre><code>- app +
      |
      + ...
- LICENSE.txt
</code></pre>

<p>Turns out this LICENSE file is a leftover file from the framework you used, but it's in the root directory of your project. The license itself is whatever license the framework is, but the copyright statement is not yours or your organizations, but the framework developers.</p>

<p>My question here is:</p>

<h3>Does this license file now somehow apply to the project?</h3>

<p>Is my project, or at least all the versions with this file in them (in the version control history), magically under this license? </p>

<p>Similarily, let's say you notice a project file (let's take <code>package.json</code>) that also has a leftover license field from somewhere that you forgot to remove:</p>

<pre><code>  "license": "ISC",
</code></pre>

<p>(I've seen this happen in JS projects where <code>npm init</code> was run through quickly, the default license field is ISC)</p>

<p>What about this? Does this somehow apply to the project, even if the author <em>intended</em> for it to be proprietary?</p>

<p>If the license file, or an associated copyright notice, clearly indicates that the license applies to the framework or package, rather then to the application developed using that tool, then it can't reasonably be construed to apply to the application.</p>

<p>It would be advisable to either remove any license files for tools used to develop the application, or if they must be there to show the license for the tool, then edit them to make sure that each indicates exactly what software the license applies to, and perhaps includes something like "This license does not apply to MyGreatApp, a separate application developed using this tool."</p>

<p>I would also suggest including a license file with the app, even if all it says is: "All rights reserved. MyGreatApp is licensed only by specific agreement with the developer." or something of the sort.</p>

software licensing