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.
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:
- app +
|
+ ...
- LICENSE.txt
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.
My question here is:
Does this license file now somehow apply to the project?
Is my project, or at least all the versions with this file in them (in the version control history), magically under this license?
Similarily, let's say you notice a project file (let's take package.json
) that also has a leftover license field from somewhere that you forgot to remove:
"license": "ISC",
(I've seen this happen in JS projects where npm init
was run through quickly, the default license field is ISC)
What about this? Does this somehow apply to the project, even if the author intended for it to be proprietary?