Bug: MPL-2.0 (dep) should be compatible with proprietary

[LSerranoPEReN]

My project is under proprietary license and I have a MPL-2.0 dependency, that is shown to be incompatible with my project.

IANAL but my understanding is that the MPL-2.0 only cares about source code modifications, so there should be no compatibility issue here, since LicenseCheck is looking at compatibility with installed packages.

Am I missing something or is this a bug?

Many thanks.

[dfeyer]

I feel the same, but I'm not a legal person ... our projet is also impacted.

[FredHappyface]

Thanks for flagging this!

Disclaimer: IANAL (I am not a lawyer )

I've done some initial research to check I'd be happy addressing this, and it does appear that the advice around MPL 2.0 is significantly more permissive than say, GPL. One source is https://opensource.stackexchange.com/questions/10493/using-of-library-under-mit-license-with-dependency-on-library-under-mpl-2-0. Here is another source that suggests this is permissibale https://opensource.stackexchange.com/questions/12068/licensing-a-library-under-the-mpl.

My take on this is that it'd be permissible to use an MPL library in an MIT/ Proprietary/ etc project as long as you disclose the lib, and provide the source/ access to the source. Before I make any changes, I'd like to consolidate my understanding best I can (as this would be a large impact change!)

For now the best option would be to include --ignore-license mpl