Can we extend license detection and find license mention in readme doc?

[vymarkov]

trafficstars

A lot of project does not contain explicit license field in package.json or license file in project's folder, currently those cases are primary maintained, but I've found a lot of projects that contain license mention like on the example below:

https://github.com/octref/polacode

Could we extend license detection method to find license mention in readme doc?

[spoenemann]

I wouldn't put that much work in detecting a project's license, but rather ask the project maintainers to fix the missing license file. The MIT license says:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

So if you're not adding a LICENSE file with the full text, you are violating that license.

[spoenemann]

The latest version of ovsx can automatically set your project's license to MIT if there isn't any. We should spread that info to project maintainers.

[vymarkov]

@spoenemann there is another case that I want to intend usage of osvx cli, I'm working on util to simplify a bit migration of extension packs that contain lots of unpublished extensions, where osvx could help to detect license and if license is not present to let know authors to add license to extension to be compliant with https://open-vsx.org ToS, then we can add an extension to https://github.com/vymarkov/publish-extensions if author doesn't want to publish it to https://open-vsx.org for some reason (doesn't have enough time, ect).

[amvanbaren]

@vymarkov Can we close this issue?