# | Rule | Package | License | Message |
---|---|---|---|---|
1 | DEPENDENCY_LICENSE_CHECK | PyPI::identify:2.5.22 | DETECTED: AGPL-3.0-only |
License AGPL-3.0-only of dependency 'PyPI::identify:2.5.22' is classified as restricted. How to fixRemove dependency 'PyPI::identify:2.5.22' from project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac'. |
2 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DECLARED: MPL-2.0 |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::certifi:2022.12.7'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::certifi:2022.12.7' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
3 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: MPL-2.0 |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::certifi:2022.12.7'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::certifi:2022.12.7' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
4 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DECLARED: MPL-2.0 |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::certifi:2022.12.7'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::certifi:2022.12.7' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
5 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: MPL-2.0 |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::certifi:2022.12.7'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::certifi:2022.12.7' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
6 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DECLARED: MPL-2.0 |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::certifi:2022.12.7'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::certifi:2022.12.7' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
7 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: MPL-2.0 |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::certifi:2022.12.7'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::certifi:2022.12.7' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
8 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DECLARED: MPL-2.0 |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::certifi:2022.12.7'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::certifi:2022.12.7' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
9 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: MPL-2.0 |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::certifi:2022.12.7'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::certifi:2022.12.7' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
10 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DECLARED: MPL-2.0 |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::certifi:2022.12.7'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::certifi:2022.12.7' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
11 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: MPL-2.0 |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::certifi:2022.12.7'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::certifi:2022.12.7' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
12 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DECLARED: MPL-2.0 |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::certifi:2022.12.7'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::certifi:2022.12.7' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
13 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: MPL-2.0 |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::certifi:2022.12.7'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::certifi:2022.12.7' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
14 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DECLARED: MPL-2.0 |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::certifi:2022.12.7'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::certifi:2022.12.7' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
15 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: MPL-2.0 |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::certifi:2022.12.7'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::certifi:2022.12.7' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
16 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DECLARED: MPL-2.0 |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::certifi:2022.12.7'. Software under a copyleft license such as the MPL-2.0 cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::certifi:2022.12.7' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
17 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: MPL-2.0 |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::certifi:2022.12.7'. Software under a copyleft license such as the MPL-2.0 cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::certifi:2022.12.7' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
18 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DECLARED: MPL-2.0 |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::certifi:2022.12.7'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::certifi:2022.12.7' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
19 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: MPL-2.0 |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::certifi:2022.12.7'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::certifi:2022.12.7' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
20 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DECLARED: MPL-2.0 |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::certifi:2022.12.7'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::certifi:2022.12.7' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
21 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: MPL-2.0 |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::certifi:2022.12.7'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::certifi:2022.12.7' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
22 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DECLARED: MPL-2.0 |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::certifi:2022.12.7'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::certifi:2022.12.7' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
23 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: MPL-2.0 |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::certifi:2022.12.7'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::certifi:2022.12.7' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
24 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LGPL-2.1-only |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::charset-normalizer:3.1.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::charset-normalizer:3.1.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
25 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LGPL-2.1-only |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::charset-normalizer:3.1.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::charset-normalizer:3.1.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
26 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LGPL-2.1-only |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::charset-normalizer:3.1.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::charset-normalizer:3.1.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
27 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LGPL-2.1-only |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::charset-normalizer:3.1.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::charset-normalizer:3.1.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
28 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LGPL-2.1-only |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::charset-normalizer:3.1.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::charset-normalizer:3.1.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
29 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LGPL-2.1-only |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::charset-normalizer:3.1.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::charset-normalizer:3.1.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
30 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LGPL-2.1-only |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::charset-normalizer:3.1.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::charset-normalizer:3.1.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
31 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LGPL-2.1-only |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::charset-normalizer:3.1.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::charset-normalizer:3.1.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
32 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LGPL-2.1-only |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::charset-normalizer:3.1.0'. Software under a copyleft license such as the LGPL-2.1-only cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::charset-normalizer:3.1.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
33 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LGPL-2.1-only |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::charset-normalizer:3.1.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::charset-normalizer:3.1.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
34 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LGPL-2.1-only |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::charset-normalizer:3.1.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::charset-normalizer:3.1.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
35 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LGPL-2.1-only |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::charset-normalizer:3.1.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::charset-normalizer:3.1.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
36 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: MPL-1.1 |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::charset-normalizer:3.1.0'. Software under a copyleft license such as the MPL-1.1 license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::charset-normalizer:3.1.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
37 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: MPL-1.1 |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::charset-normalizer:3.1.0'. Software under a copyleft license such as the MPL-1.1 license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::charset-normalizer:3.1.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
38 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: MPL-1.1 |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::charset-normalizer:3.1.0'. Software under a copyleft license such as the MPL-1.1 license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::charset-normalizer:3.1.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
39 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: MPL-1.1 |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::charset-normalizer:3.1.0'. Software under a copyleft license such as the MPL-1.1 license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::charset-normalizer:3.1.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
40 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: MPL-1.1 |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::charset-normalizer:3.1.0'. Software under a copyleft license such as the MPL-1.1 license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::charset-normalizer:3.1.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
41 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: MPL-1.1 |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::charset-normalizer:3.1.0'. Software under a copyleft license such as the MPL-1.1 license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::charset-normalizer:3.1.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
42 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: MPL-1.1 |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::charset-normalizer:3.1.0'. Software under a copyleft license such as the MPL-1.1 license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::charset-normalizer:3.1.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
43 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: MPL-1.1 |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::charset-normalizer:3.1.0'. Software under a copyleft license such as the MPL-1.1 license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::charset-normalizer:3.1.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
44 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: MPL-1.1 |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::charset-normalizer:3.1.0'. Software under a copyleft license such as the MPL-1.1 cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::charset-normalizer:3.1.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
45 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: MPL-1.1 |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::charset-normalizer:3.1.0'. Software under a copyleft license such as the MPL-1.1 license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::charset-normalizer:3.1.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
46 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: MPL-1.1 |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::charset-normalizer:3.1.0'. Software under a copyleft license such as the MPL-1.1 license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::charset-normalizer:3.1.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
47 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: MPL-1.1 |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::charset-normalizer:3.1.0'. Software under a copyleft license such as the MPL-1.1 license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::charset-normalizer:3.1.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
48 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: GPL-3.0-only |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::conan:1.58.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::conan:1.58.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
49 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: GPL-3.0-only |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::conan:1.58.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::conan:1.58.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
50 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: GPL-3.0-only |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::conan:1.58.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::conan:1.58.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
51 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: GPL-3.0-only |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::conan:1.58.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::conan:1.58.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
52 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: GPL-3.0-only |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::conan:1.58.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::conan:1.58.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
53 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: GPL-3.0-only |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::conan:1.58.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::conan:1.58.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
54 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: GPL-3.0-only |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::conan:1.58.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::conan:1.58.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
55 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: GPL-3.0-only |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::conan:1.58.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::conan:1.58.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
56 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: GPL-3.0-only |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::conan:1.58.0'. Software under a copyleft license such as the GPL-3.0-only cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::conan:1.58.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
57 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: GPL-3.0-only |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::conan:1.58.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::conan:1.58.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
58 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: GPL-3.0-only |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::conan:1.58.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::conan:1.58.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
59 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: GPL-3.0-only |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::conan:1.58.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::conan:1.58.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
60 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: GPL-2.0-only |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::cpplint:1.6.1'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::cpplint:1.6.1' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
61 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: GPL-2.0-only |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::cpplint:1.6.1'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::cpplint:1.6.1' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
62 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: GPL-2.0-only |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::cpplint:1.6.1'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::cpplint:1.6.1' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
63 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: GPL-2.0-only |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::cpplint:1.6.1'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::cpplint:1.6.1' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
64 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: GPL-2.0-only |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::cpplint:1.6.1'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::cpplint:1.6.1' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
65 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: GPL-2.0-only |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::cpplint:1.6.1'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::cpplint:1.6.1' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
66 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: GPL-2.0-only |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::cpplint:1.6.1'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::cpplint:1.6.1' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
67 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: GPL-2.0-only |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::cpplint:1.6.1'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::cpplint:1.6.1' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
68 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: GPL-2.0-only |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::cpplint:1.6.1'. Software under a copyleft license such as the GPL-2.0-only cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::cpplint:1.6.1' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
69 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: GPL-2.0-only |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::cpplint:1.6.1'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::cpplint:1.6.1' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
70 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: GPL-2.0-only |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::cpplint:1.6.1'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::cpplint:1.6.1' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
71 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: GPL-2.0-only |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::cpplint:1.6.1'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::cpplint:1.6.1' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
72 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: LGPL-2.1-or-later |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::cpplint:1.6.1'. Software under a copyleft license such as the LGPL-2.1-or-later license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::cpplint:1.6.1' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
73 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: LGPL-2.1-or-later |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::cpplint:1.6.1'. Software under a copyleft license such as the LGPL-2.1-or-later license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::cpplint:1.6.1' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
74 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: LGPL-2.1-or-later |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::cpplint:1.6.1'. Software under a copyleft license such as the LGPL-2.1-or-later license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::cpplint:1.6.1' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
75 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: LGPL-2.1-or-later |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::cpplint:1.6.1'. Software under a copyleft license such as the LGPL-2.1-or-later license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::cpplint:1.6.1' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
76 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: LGPL-2.1-or-later |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::cpplint:1.6.1'. Software under a copyleft license such as the LGPL-2.1-or-later license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::cpplint:1.6.1' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
77 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: LGPL-2.1-or-later |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::cpplint:1.6.1'. Software under a copyleft license such as the LGPL-2.1-or-later license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::cpplint:1.6.1' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
78 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: LGPL-2.1-or-later |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::cpplint:1.6.1'. Software under a copyleft license such as the LGPL-2.1-or-later license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::cpplint:1.6.1' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
79 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: LGPL-2.1-or-later |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::cpplint:1.6.1'. Software under a copyleft license such as the LGPL-2.1-or-later license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::cpplint:1.6.1' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
80 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: LGPL-2.1-or-later |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::cpplint:1.6.1'. Software under a copyleft license such as the LGPL-2.1-or-later cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::cpplint:1.6.1' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
81 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: LGPL-2.1-or-later |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::cpplint:1.6.1'. Software under a copyleft license such as the LGPL-2.1-or-later license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::cpplint:1.6.1' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
82 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: LGPL-2.1-or-later |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::cpplint:1.6.1'. Software under a copyleft license such as the LGPL-2.1-or-later license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::cpplint:1.6.1' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
83 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: LGPL-2.1-or-later |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::cpplint:1.6.1'. Software under a copyleft license such as the LGPL-2.1-or-later license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::cpplint:1.6.1' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
84 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: AGPL-3.0-only |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license AGPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the AGPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
85 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: AGPL-3.0-only |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license AGPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the AGPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
86 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: AGPL-3.0-only |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license AGPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the AGPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
87 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: AGPL-3.0-only |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license AGPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the AGPL-3.0-only license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
88 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: AGPL-3.0-only |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license AGPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the AGPL-3.0-only license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
89 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: AGPL-3.0-only |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license AGPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the AGPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
90 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: AGPL-3.0-only |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license AGPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the AGPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
91 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: AGPL-3.0-only |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license AGPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the AGPL-3.0-only license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
92 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: AGPL-3.0-only |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license AGPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the AGPL-3.0-only cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
93 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: AGPL-3.0-only |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license AGPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the AGPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
94 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: AGPL-3.0-only |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license AGPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the AGPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
95 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: AGPL-3.0-only |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license AGPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the AGPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
96 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EPL-1.0 |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-1.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EPL-1.0 license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
97 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EPL-1.0 |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-1.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EPL-1.0 license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
98 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EPL-1.0 |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-1.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EPL-1.0 license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
99 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EPL-1.0 |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-1.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EPL-1.0 license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
100 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EPL-1.0 |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-1.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EPL-1.0 license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
101 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EPL-1.0 |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-1.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EPL-1.0 license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
102 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EPL-1.0 |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-1.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EPL-1.0 cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
103 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EPL-1.0 |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-1.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EPL-1.0 license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
104 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EPL-1.0 |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-1.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EPL-1.0 license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
105 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EPL-1.0 |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-1.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EPL-1.0 license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
106 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EPL-2.0 |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-2.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
107 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EPL-2.0 |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-2.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
108 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EPL-2.0 |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-2.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
109 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EPL-2.0 |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-2.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EPL-2.0 license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
110 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EPL-2.0 |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-2.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
111 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EPL-2.0 |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-2.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
112 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EPL-2.0 |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-2.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EPL-2.0 license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
113 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EPL-2.0 |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-2.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EPL-2.0 cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
114 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EPL-2.0 |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-2.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
115 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EPL-2.0 |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-2.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
116 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EPL-2.0 |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-2.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
117 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EUPL-1.1 |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EUPL-1.1 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EUPL-1.1 license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
118 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EUPL-1.1 |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EUPL-1.1 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EUPL-1.1 license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
119 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EUPL-1.1 |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EUPL-1.1 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EUPL-1.1 license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
120 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EUPL-1.1 |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EUPL-1.1 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EUPL-1.1 license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
121 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EUPL-1.1 |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EUPL-1.1 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EUPL-1.1 license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
122 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EUPL-1.1 |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EUPL-1.1 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EUPL-1.1 license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
123 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EUPL-1.1 |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EUPL-1.1 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EUPL-1.1 license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
124 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EUPL-1.1 |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EUPL-1.1 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EUPL-1.1 cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
125 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EUPL-1.1 |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EUPL-1.1 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EUPL-1.1 license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
126 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EUPL-1.1 |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EUPL-1.1 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EUPL-1.1 license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
127 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EUPL-1.1 |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EUPL-1.1 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EUPL-1.1 license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
128 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EUPL-1.2 |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EUPL-1.2 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EUPL-1.2 license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
129 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EUPL-1.2 |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EUPL-1.2 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EUPL-1.2 license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
130 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EUPL-1.2 |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EUPL-1.2 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EUPL-1.2 license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
131 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EUPL-1.2 |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EUPL-1.2 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EUPL-1.2 license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
132 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EUPL-1.2 |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EUPL-1.2 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EUPL-1.2 license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
133 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EUPL-1.2 |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EUPL-1.2 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EUPL-1.2 license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
134 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EUPL-1.2 |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EUPL-1.2 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EUPL-1.2 license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
135 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EUPL-1.2 |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EUPL-1.2 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EUPL-1.2 license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
136 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EUPL-1.2 |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EUPL-1.2 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EUPL-1.2 cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
137 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EUPL-1.2 |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EUPL-1.2 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EUPL-1.2 license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
138 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EUPL-1.2 |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EUPL-1.2 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EUPL-1.2 license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
139 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EUPL-1.2 |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EUPL-1.2 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the EUPL-1.2 license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
140 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-1.0-or-later |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
141 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-1.0-or-later |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
142 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-1.0-or-later |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
143 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-1.0-or-later |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
144 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-1.0-or-later |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
145 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-1.0-or-later |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
146 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-1.0-or-later |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
147 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-1.0-or-later |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
148 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-1.0-or-later |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-1.0-or-later cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
149 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-1.0-or-later |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
150 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-1.0-or-later |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
151 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-1.0-or-later |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
152 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-2.0-only |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
153 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-2.0-only |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
154 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-2.0-only |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
155 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-2.0-only |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
156 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-2.0-only |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
157 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-2.0-only |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
158 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-2.0-only |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
159 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-2.0-only |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
160 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-2.0-only |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-2.0-only cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
161 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-2.0-only |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
162 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-2.0-only |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
163 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-2.0-only |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
164 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-3.0-only |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
165 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-3.0-only |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
166 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-3.0-only |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
167 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-3.0-only |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
168 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-3.0-only |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
169 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-3.0-only |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
170 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-3.0-only |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
171 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-3.0-only |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
172 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-3.0-only |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-3.0-only cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
173 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-3.0-only |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
174 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-3.0-only |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
175 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-3.0-only |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
176 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LGPL-2.1-only |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
177 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LGPL-2.1-only |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
178 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LGPL-2.1-only |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
179 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LGPL-2.1-only |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
180 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LGPL-2.1-only |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
181 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LGPL-2.1-only |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
182 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LGPL-2.1-only |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
183 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LGPL-2.1-only |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
184 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LGPL-2.1-only |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the LGPL-2.1-only cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
185 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LGPL-2.1-only |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
186 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LGPL-2.1-only |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
187 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LGPL-2.1-only |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
188 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LGPL-3.0-only |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the LGPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
189 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LGPL-3.0-only |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the LGPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
190 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LGPL-3.0-only |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the LGPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
191 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LGPL-3.0-only |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the LGPL-3.0-only license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
192 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LGPL-3.0-only |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the LGPL-3.0-only license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
193 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LGPL-3.0-only |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the LGPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
194 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LGPL-3.0-only |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the LGPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
195 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LGPL-3.0-only |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the LGPL-3.0-only license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
196 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LGPL-3.0-only |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the LGPL-3.0-only cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
197 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LGPL-3.0-only |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the LGPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
198 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LGPL-3.0-only |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the LGPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
199 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LGPL-3.0-only |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the LGPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
200 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MPL-2.0 |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
201 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MPL-2.0 |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
202 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MPL-2.0 |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
203 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MPL-2.0 |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
204 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MPL-2.0 |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
205 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MPL-2.0 |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
206 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MPL-2.0 |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
207 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MPL-2.0 |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the MPL-2.0 cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
208 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MPL-2.0 |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
209 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MPL-2.0 |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
210 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MPL-2.0 |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
211 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MS-RL |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MS-RL of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the MS-RL license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
212 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MS-RL |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MS-RL of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the MS-RL license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
213 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MS-RL |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MS-RL of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the MS-RL license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
214 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MS-RL |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MS-RL of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the MS-RL license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
215 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MS-RL |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MS-RL of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the MS-RL license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
216 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MS-RL |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MS-RL of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the MS-RL license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
217 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MS-RL |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MS-RL of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the MS-RL license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
218 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MS-RL |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MS-RL of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the MS-RL license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
219 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MS-RL |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MS-RL of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the MS-RL cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
220 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MS-RL |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MS-RL of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the MS-RL license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
221 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MS-RL |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MS-RL of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the MS-RL license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
222 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MS-RL |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MS-RL of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the MS-RL license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
223 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: OSL-3.0 |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license OSL-3.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the OSL-3.0 license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
224 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: OSL-3.0 |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license OSL-3.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the OSL-3.0 license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
225 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: OSL-3.0 |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license OSL-3.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the OSL-3.0 license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
226 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: OSL-3.0 |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license OSL-3.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the OSL-3.0 license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
227 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: OSL-3.0 |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license OSL-3.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the OSL-3.0 license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
228 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: OSL-3.0 |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license OSL-3.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the OSL-3.0 license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
229 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: OSL-3.0 |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license OSL-3.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the OSL-3.0 license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
230 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: OSL-3.0 |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license OSL-3.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the OSL-3.0 license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
231 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: OSL-3.0 |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license OSL-3.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the OSL-3.0 cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
232 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: OSL-3.0 |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license OSL-3.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the OSL-3.0 license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
233 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: OSL-3.0 |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license OSL-3.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the OSL-3.0 license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
234 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: OSL-3.0 |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license OSL-3.0 of its dependency 'PyPI::identify:2.5.22'. Software under a copyleft license such as the OSL-3.0 license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::identify:2.5.22' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
235 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-1.0-or-later |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
236 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-1.0-or-later |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
237 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-1.0-or-later |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
238 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-1.0-or-later |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
239 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-1.0-or-later |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
240 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-1.0-or-later |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
241 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-1.0-or-later |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
242 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-1.0-or-later |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
243 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-1.0-or-later |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-1.0-or-later cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
244 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-1.0-or-later |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
245 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-1.0-or-later |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
246 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-1.0-or-later |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
247 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-2.0-only |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
248 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-2.0-only |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
249 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-2.0-only |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
250 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-2.0-only |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
251 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-2.0-only |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
252 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-2.0-only |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
253 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-2.0-only |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
254 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-2.0-only |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
255 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-2.0-only |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-2.0-only cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
256 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-2.0-only |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
257 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-2.0-only |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
258 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-2.0-only |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
259 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-2.0-or-later |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
260 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-2.0-or-later |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
261 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-2.0-or-later |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
262 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-2.0-or-later |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
263 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-2.0-or-later |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
264 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-2.0-or-later |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
265 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-2.0-or-later |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
266 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-2.0-or-later |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
267 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-2.0-or-later |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-2.0-or-later cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
268 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-2.0-or-later |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
269 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-2.0-or-later |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
270 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-2.0-or-later |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::lxml:4.9.2'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::lxml:4.9.2' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
271 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: GPL-1.0-or-later |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::patch-ng:1.17.4'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::patch-ng:1.17.4' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
272 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: GPL-1.0-or-later |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::patch-ng:1.17.4'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::patch-ng:1.17.4' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
273 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: GPL-1.0-or-later |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::patch-ng:1.17.4'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::patch-ng:1.17.4' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
274 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: GPL-1.0-or-later |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::patch-ng:1.17.4'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::patch-ng:1.17.4' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
275 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: GPL-1.0-or-later |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::patch-ng:1.17.4'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::patch-ng:1.17.4' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
276 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: GPL-1.0-or-later |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::patch-ng:1.17.4'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::patch-ng:1.17.4' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
277 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: GPL-1.0-or-later |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::patch-ng:1.17.4'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::patch-ng:1.17.4' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
278 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: GPL-1.0-or-later |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::patch-ng:1.17.4'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::patch-ng:1.17.4' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
279 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: GPL-1.0-or-later |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::patch-ng:1.17.4'. Software under a copyleft license such as the GPL-1.0-or-later cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::patch-ng:1.17.4' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
280 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: GPL-1.0-or-later |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::patch-ng:1.17.4'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::patch-ng:1.17.4' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
281 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: GPL-1.0-or-later |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::patch-ng:1.17.4'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::patch-ng:1.17.4' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
282 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: GPL-1.0-or-later |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::patch-ng:1.17.4'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::patch-ng:1.17.4' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
283 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: GPL-3.0-only |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::patch-ng:1.17.4'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::patch-ng:1.17.4' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
284 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: GPL-3.0-only |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::patch-ng:1.17.4'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::patch-ng:1.17.4' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
285 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: GPL-3.0-only |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::patch-ng:1.17.4'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::patch-ng:1.17.4' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
286 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: GPL-3.0-only |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::patch-ng:1.17.4'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::patch-ng:1.17.4' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
287 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: GPL-3.0-only |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::patch-ng:1.17.4'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::patch-ng:1.17.4' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
288 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: GPL-3.0-only |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::patch-ng:1.17.4'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::patch-ng:1.17.4' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
289 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: GPL-3.0-only |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::patch-ng:1.17.4'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::patch-ng:1.17.4' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
290 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: GPL-3.0-only |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::patch-ng:1.17.4'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::patch-ng:1.17.4' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
291 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: GPL-3.0-only |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::patch-ng:1.17.4'. Software under a copyleft license such as the GPL-3.0-only cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::patch-ng:1.17.4' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
292 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: GPL-3.0-only |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::patch-ng:1.17.4'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::patch-ng:1.17.4' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
293 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: GPL-3.0-only |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::patch-ng:1.17.4'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::patch-ng:1.17.4' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
294 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: GPL-3.0-only |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::patch-ng:1.17.4'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::patch-ng:1.17.4' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
295 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pre-commit:2.20.0 | DETECTED: GPL-3.0-only |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::pre-commit:2.20.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pre-commit:2.20.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
296 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pre-commit:2.20.0 | DETECTED: GPL-3.0-only |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::pre-commit:2.20.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pre-commit:2.20.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
297 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pre-commit:2.20.0 | DETECTED: GPL-3.0-only |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::pre-commit:2.20.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pre-commit:2.20.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
298 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pre-commit:2.20.0 | DETECTED: GPL-3.0-only |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::pre-commit:2.20.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pre-commit:2.20.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
299 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pre-commit:2.20.0 | DETECTED: GPL-3.0-only |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::pre-commit:2.20.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pre-commit:2.20.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
300 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pre-commit:2.20.0 | DETECTED: GPL-3.0-only |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::pre-commit:2.20.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pre-commit:2.20.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
301 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pre-commit:2.20.0 | DETECTED: GPL-3.0-only |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::pre-commit:2.20.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pre-commit:2.20.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
302 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pre-commit:2.20.0 | DETECTED: GPL-3.0-only |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::pre-commit:2.20.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pre-commit:2.20.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
303 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pre-commit:2.20.0 | DETECTED: GPL-3.0-only |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::pre-commit:2.20.0'. Software under a copyleft license such as the GPL-3.0-only cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::pre-commit:2.20.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
304 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pre-commit:2.20.0 | DETECTED: GPL-3.0-only |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::pre-commit:2.20.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pre-commit:2.20.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
305 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pre-commit:2.20.0 | DETECTED: GPL-3.0-only |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::pre-commit:2.20.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pre-commit:2.20.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
306 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pre-commit:2.20.0 | DETECTED: GPL-3.0-only |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::pre-commit:2.20.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pre-commit:2.20.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
307 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: CPL-1.0 |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license CPL-1.0 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the CPL-1.0 license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
308 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: CPL-1.0 |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license CPL-1.0 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the CPL-1.0 license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
309 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: CPL-1.0 |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license CPL-1.0 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the CPL-1.0 license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
310 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: CPL-1.0 |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license CPL-1.0 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the CPL-1.0 license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
311 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: CPL-1.0 |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license CPL-1.0 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the CPL-1.0 license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
312 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: CPL-1.0 |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license CPL-1.0 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the CPL-1.0 license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
313 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: CPL-1.0 |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license CPL-1.0 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the CPL-1.0 cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
314 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: CPL-1.0 |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license CPL-1.0 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the CPL-1.0 license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
315 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: CPL-1.0 |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license CPL-1.0 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the CPL-1.0 license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
316 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: CPL-1.0 |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license CPL-1.0 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the CPL-1.0 license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
317 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-1.0-or-later |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
318 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-1.0-or-later |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
319 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-1.0-or-later |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
320 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-1.0-or-later |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
321 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-1.0-or-later |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
322 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-1.0-or-later |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
323 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-1.0-or-later |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
324 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-1.0-or-later |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
325 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-1.0-or-later |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-1.0-or-later cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
326 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-1.0-or-later |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
327 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-1.0-or-later |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
328 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-1.0-or-later |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-1.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
329 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-only |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
330 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-only |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
331 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-only |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
332 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-only |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
333 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-only |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
334 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-only |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
335 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-only |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
336 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-only |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
337 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-only |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-only cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
338 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-only |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
339 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-only |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
340 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-only |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
341 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
342 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
343 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
344 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
345 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
346 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
347 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
348 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
349 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
350 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
351 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
352 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
353 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0 |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
354 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0 |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
355 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0 |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
356 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0 |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
357 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0 |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
358 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0 |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
359 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0 |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
360 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0 |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
361 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0 |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
362 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0 |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
363 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0 |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
364 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0 |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
365 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0 |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
366 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0 |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
367 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0 |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
368 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0 |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
369 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0 |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
370 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0 |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
371 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0 |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
372 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0 |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
373 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0 |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
374 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0 |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
375 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0 |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
376 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0 |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
377 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0 |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
378 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0 |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
379 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0 |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
380 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0 |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
381 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0 |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
382 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0 |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
383 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0 |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
384 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0 |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
385 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0 |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
386 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0 |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
387 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0 |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
388 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0 |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-2.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
389 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-3.0-only |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
390 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-3.0-only |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
391 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-3.0-only |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
392 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-3.0-only |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
393 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-3.0-only |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
394 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-3.0-only |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
395 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-3.0-only |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
396 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-3.0-only |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
397 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-3.0-only |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-3.0-only cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
398 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-3.0-only |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
399 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-3.0-only |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
400 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-3.0-only |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
401 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-3.0-or-later |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-3.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
402 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-3.0-or-later |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-3.0-or-later license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
403 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-3.0-or-later |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-3.0-or-later license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
404 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-3.0-or-later |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-3.0-or-later license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
405 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-3.0-or-later |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-3.0-or-later license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
406 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-3.0-or-later |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-3.0-or-later license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
407 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-3.0-or-later |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-3.0-or-later license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
408 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-3.0-or-later |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-3.0-or-later license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
409 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-3.0-or-later |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-3.0-or-later cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
410 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-3.0-or-later |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-3.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
411 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-3.0-or-later |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-3.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
412 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-3.0-or-later |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the GPL-3.0-or-later license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
413 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-only |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
414 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-only |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
415 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-only |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
416 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-only |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
417 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-only |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
418 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-only |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
419 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-only |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
420 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-only |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
421 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-only |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-only cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
422 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-only |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
423 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-only |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
424 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-only |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
425 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-only WITH Qt-LGPL-exception-1.1 |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only (simplified from 'LGPL-2.1-only WITH Qt-LGPL-exception-1.1') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
426 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-only WITH Qt-LGPL-exception-1.1 |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only (simplified from 'LGPL-2.1-only WITH Qt-LGPL-exception-1.1') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
427 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-only WITH Qt-LGPL-exception-1.1 |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only (simplified from 'LGPL-2.1-only WITH Qt-LGPL-exception-1.1') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
428 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-only WITH Qt-LGPL-exception-1.1 |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only (simplified from 'LGPL-2.1-only WITH Qt-LGPL-exception-1.1') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
429 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-only WITH Qt-LGPL-exception-1.1 |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only (simplified from 'LGPL-2.1-only WITH Qt-LGPL-exception-1.1') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
430 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-only WITH Qt-LGPL-exception-1.1 |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only (simplified from 'LGPL-2.1-only WITH Qt-LGPL-exception-1.1') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
431 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-only WITH Qt-LGPL-exception-1.1 |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only (simplified from 'LGPL-2.1-only WITH Qt-LGPL-exception-1.1') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
432 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-only WITH Qt-LGPL-exception-1.1 |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only (simplified from 'LGPL-2.1-only WITH Qt-LGPL-exception-1.1') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
433 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-only WITH Qt-LGPL-exception-1.1 |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only (simplified from 'LGPL-2.1-only WITH Qt-LGPL-exception-1.1') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-only cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
434 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-only WITH Qt-LGPL-exception-1.1 |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only (simplified from 'LGPL-2.1-only WITH Qt-LGPL-exception-1.1') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
435 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-only WITH Qt-LGPL-exception-1.1 |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only (simplified from 'LGPL-2.1-only WITH Qt-LGPL-exception-1.1') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
436 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-only WITH Qt-LGPL-exception-1.1 |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-only (simplified from 'LGPL-2.1-only WITH Qt-LGPL-exception-1.1') of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
437 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-or-later |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-or-later license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
438 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-or-later |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-or-later license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
439 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-or-later |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-or-later license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
440 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-or-later |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-or-later license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
441 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-or-later |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-or-later license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
442 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-or-later |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-or-later license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
443 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-or-later |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-or-later license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
444 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-or-later |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-or-later license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
445 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-or-later |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-or-later cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
446 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-or-later |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-or-later license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
447 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-or-later |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-or-later license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
448 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-or-later |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-2.1-or-later license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
449 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-3.0-only |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-3.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
450 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-3.0-only |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-3.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
451 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-3.0-only |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-3.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
452 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-3.0-only |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-3.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-3.0-only license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
453 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-3.0-only |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-3.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-3.0-only license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
454 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-3.0-only |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-3.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
455 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-3.0-only |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-3.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
456 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-3.0-only |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-3.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-3.0-only license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
457 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-3.0-only |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-3.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-3.0-only cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
458 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-3.0-only |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-3.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
459 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-3.0-only |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-3.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
460 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-3.0-only |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license LGPL-3.0-only of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the LGPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
461 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MPL-1.1 |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the MPL-1.1 license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
462 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MPL-1.1 |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the MPL-1.1 license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
463 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MPL-1.1 |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the MPL-1.1 license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
464 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MPL-1.1 |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the MPL-1.1 license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
465 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MPL-1.1 |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the MPL-1.1 license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
466 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MPL-1.1 |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the MPL-1.1 license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
467 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MPL-1.1 |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the MPL-1.1 license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
468 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MPL-1.1 |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the MPL-1.1 license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
469 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MPL-1.1 |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the MPL-1.1 cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
470 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MPL-1.1 |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the MPL-1.1 license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
471 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MPL-1.1 |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the MPL-1.1 license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
472 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MPL-1.1 |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the MPL-1.1 license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
473 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MPL-2.0 |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
474 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MPL-2.0 |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
475 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MPL-2.0 |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
476 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MPL-2.0 |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
477 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MPL-2.0 |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
478 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MPL-2.0 |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
479 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MPL-2.0 |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
480 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MPL-2.0 |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the MPL-2.0 cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
481 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MPL-2.0 |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
482 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MPL-2.0 |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
483 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MPL-2.0 |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::pygments:2.14.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pygments:2.14.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
484 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: GPL-3.0-only |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::setuptools:67.6.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::setuptools:67.6.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
485 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: GPL-3.0-only |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::setuptools:67.6.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::setuptools:67.6.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
486 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: GPL-3.0-only |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::setuptools:67.6.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::setuptools:67.6.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
487 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: GPL-3.0-only |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::setuptools:67.6.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::setuptools:67.6.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
488 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: GPL-3.0-only |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::setuptools:67.6.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::setuptools:67.6.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
489 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: GPL-3.0-only |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::setuptools:67.6.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::setuptools:67.6.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
490 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: GPL-3.0-only |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::setuptools:67.6.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::setuptools:67.6.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
491 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: GPL-3.0-only |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::setuptools:67.6.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::setuptools:67.6.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
492 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: GPL-3.0-only |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::setuptools:67.6.0'. Software under a copyleft license such as the GPL-3.0-only cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::setuptools:67.6.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
493 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: GPL-3.0-only |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::setuptools:67.6.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::setuptools:67.6.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
494 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: GPL-3.0-only |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::setuptools:67.6.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::setuptools:67.6.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
495 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: GPL-3.0-only |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::setuptools:67.6.0'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::setuptools:67.6.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
496 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: MPL-2.0 |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::setuptools:67.6.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::setuptools:67.6.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
497 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: MPL-2.0 |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::setuptools:67.6.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::setuptools:67.6.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
498 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: MPL-2.0 |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::setuptools:67.6.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::setuptools:67.6.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
499 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: MPL-2.0 |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::setuptools:67.6.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::setuptools:67.6.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
500 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: MPL-2.0 |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::setuptools:67.6.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::setuptools:67.6.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
501 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: MPL-2.0 |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::setuptools:67.6.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::setuptools:67.6.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
502 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: MPL-2.0 |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::setuptools:67.6.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::setuptools:67.6.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
503 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: MPL-2.0 |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::setuptools:67.6.0'. Software under a copyleft license such as the MPL-2.0 cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::setuptools:67.6.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
504 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: MPL-2.0 |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::setuptools:67.6.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::setuptools:67.6.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
505 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: MPL-2.0 |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::setuptools:67.6.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::setuptools:67.6.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
506 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: MPL-2.0 |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::setuptools:67.6.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::setuptools:67.6.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
507 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DECLARED: MPL-2.0 |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::tqdm:4.65.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::tqdm:4.65.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
508 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DETECTED: MPL-2.0 |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::tqdm:4.65.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::tqdm:4.65.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
509 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DECLARED: MPL-2.0 |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::tqdm:4.65.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::tqdm:4.65.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
510 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DETECTED: MPL-2.0 |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::tqdm:4.65.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::tqdm:4.65.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
511 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DECLARED: MPL-2.0 |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::tqdm:4.65.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::tqdm:4.65.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
512 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DETECTED: MPL-2.0 |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::tqdm:4.65.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::tqdm:4.65.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
513 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DECLARED: MPL-2.0 |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::tqdm:4.65.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::tqdm:4.65.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
514 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DETECTED: MPL-2.0 |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::tqdm:4.65.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under another copyleft license such as the EPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::tqdm:4.65.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
515 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DECLARED: MPL-2.0 |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::tqdm:4.65.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::tqdm:4.65.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
516 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DETECTED: MPL-2.0 |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::tqdm:4.65.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under another copyleft license such as the EPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::tqdm:4.65.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
517 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DECLARED: MPL-2.0 |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::tqdm:4.65.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::tqdm:4.65.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
518 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DETECTED: MPL-2.0 |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::tqdm:4.65.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::tqdm:4.65.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
519 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DECLARED: MPL-2.0 |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::tqdm:4.65.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::tqdm:4.65.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
520 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DETECTED: MPL-2.0 |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::tqdm:4.65.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::tqdm:4.65.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
521 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DECLARED: MPL-2.0 |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::tqdm:4.65.0'. Software under a copyleft license such as the MPL-2.0 cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::tqdm:4.65.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
522 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DETECTED: MPL-2.0 |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::tqdm:4.65.0'. Software under a copyleft license such as the MPL-2.0 cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::tqdm:4.65.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
523 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DECLARED: MPL-2.0 |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::tqdm:4.65.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::tqdm:4.65.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
524 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DETECTED: MPL-2.0 |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::tqdm:4.65.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::tqdm:4.65.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
525 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DECLARED: MPL-2.0 |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::tqdm:4.65.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::tqdm:4.65.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
526 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DETECTED: MPL-2.0 |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::tqdm:4.65.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::tqdm:4.65.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
527 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DECLARED: MPL-2.0 |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::tqdm:4.65.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::tqdm:4.65.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
528 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DETECTED: MPL-2.0 |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::tqdm:4.65.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::tqdm:4.65.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
529 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::virtualenv:20.21.0 | DETECTED: EPL-1.0 |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-1.0 of its dependency 'PyPI::virtualenv:20.21.0'. Software under a copyleft license such as the EPL-1.0 license normally cannot be redistributed under a non-copyleft license such as the Apache-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::virtualenv:20.21.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
530 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::virtualenv:20.21.0 | DETECTED: EPL-1.0 |
The outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-1.0 of its dependency 'PyPI::virtualenv:20.21.0'. Software under a copyleft license such as the EPL-1.0 license normally cannot be redistributed under a non-copyleft license such as the BSD-2-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::virtualenv:20.21.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
531 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::virtualenv:20.21.0 | DETECTED: EPL-1.0 |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-1.0 of its dependency 'PyPI::virtualenv:20.21.0'. Software under a copyleft license such as the EPL-1.0 license normally cannot be redistributed under a non-copyleft license such as the BSD-3-Clause license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::virtualenv:20.21.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
532 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::virtualenv:20.21.0 | DETECTED: EPL-1.0 |
The outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-1.0 of its dependency 'PyPI::virtualenv:20.21.0'. Software under a copyleft license such as the EPL-1.0 license normally cannot be redistributed under a non-copyleft license such as the ISC license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::virtualenv:20.21.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
533 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::virtualenv:20.21.0 | DETECTED: EPL-1.0 |
The outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-1.0 of its dependency 'PyPI::virtualenv:20.21.0'. Software under a copyleft license such as the EPL-1.0 license normally cannot be redistributed under a non-copyleft license such as the MIT license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::virtualenv:20.21.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
534 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::virtualenv:20.21.0 | DETECTED: EPL-1.0 |
The outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-1.0 of its dependency 'PyPI::virtualenv:20.21.0'. Software under a copyleft license such as the EPL-1.0 license normally cannot be redistributed under another copyleft license such as the MPL-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::virtualenv:20.21.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
535 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::virtualenv:20.21.0 | DETECTED: EPL-1.0 |
The outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-1.0 of its dependency 'PyPI::virtualenv:20.21.0'. Software under a copyleft license such as the EPL-1.0 cannot be redistributed under the OpenSSL license even if the OpenSSL were considered to have no copyleft clause. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixRemove the dependency on 'PyPI::virtualenv:20.21.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
536 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::virtualenv:20.21.0 | DETECTED: EPL-1.0 |
The outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-1.0 of its dependency 'PyPI::virtualenv:20.21.0'. Software under a copyleft license such as the EPL-1.0 license normally cannot be redistributed under a non-copyleft license such as the Python-2.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::virtualenv:20.21.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
537 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::virtualenv:20.21.0 | DETECTED: EPL-1.0 |
The outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-1.0 of its dependency 'PyPI::virtualenv:20.21.0'. Software under a copyleft license such as the EPL-1.0 license normally cannot be redistributed under a non-copyleft license such as the Unlicense license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::virtualenv:20.21.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
538 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::virtualenv:20.21.0 | DETECTED: EPL-1.0 |
The outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is incompatible with the inbound license EPL-1.0 of its dependency 'PyPI::virtualenv:20.21.0'. Software under a copyleft license such as the EPL-1.0 license normally cannot be redistributed under a non-copyleft license such as the Zlib license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::virtualenv:20.21.0' or put 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' under a different license. |
539 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::bottle:0.12.25 | DECLARED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::bottle:0.12.25'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
540 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::bottle:0.12.25 | DETECTED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::bottle:0.12.25'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
541 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DECLARED: MPL-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MPL-2.0 of its dependency 'PyPI::certifi:2022.12.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
542 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: MPL-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MPL-2.0 of its dependency 'PyPI::certifi:2022.12.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
543 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: Python-2.0 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::certifi:2022.12.7'. There is insufficient information or knowledge whether the Python-2.0 license is compatible with the EPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the EPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
544 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: Python-2.0 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::certifi:2022.12.7'. There is insufficient information or knowledge whether the Python-2.0 license is compatible with the EPL-2.0 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the EPL-2.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
545 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: Python-2.0 |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::certifi:2022.12.7'. There is insufficient information or knowledge whether the Python-2.0 license is compatible with the MPL-2.0 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the MPL-2.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
546 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: Python-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::certifi:2022.12.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
547 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: Python-2.0 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::certifi:2022.12.7'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
548 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cfgv:3.3.1 | DECLARED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::cfgv:3.3.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
549 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cfgv:3.3.1 | DETECTED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::cfgv:3.3.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
550 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: CC-BY-SA-3.0 |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-SA-3.0 of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
551 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: CC-BY-SA-3.0 |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-SA-3.0 of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
552 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: CC-BY-SA-3.0 |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-SA-3.0 of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
553 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: CC-BY-SA-3.0 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-SA-3.0 of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
554 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: CC-BY-SA-3.0 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-SA-3.0 of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
555 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: CC-BY-SA-3.0 |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-SA-3.0 of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
556 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: CC-BY-SA-3.0 |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-SA-3.0 of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
557 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: CC-BY-SA-3.0 |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-SA-3.0 of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
558 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: CC-BY-SA-3.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-SA-3.0 of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
559 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: CC-BY-SA-3.0 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-SA-3.0 of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
560 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: CC-BY-SA-3.0 |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-SA-3.0 of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
561 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: CC-BY-SA-3.0 |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-SA-3.0 of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
562 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: CC-BY-SA-3.0 |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-SA-3.0 of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
563 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LGPL-2.1-only |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
564 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
565 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
566 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
567 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
568 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
569 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
570 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
571 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
572 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
573 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
574 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
575 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
576 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
577 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DECLARED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
578 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
579 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: MPL-1.1 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MPL-1.1 of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
580 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
581 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
582 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
583 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
584 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
585 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
586 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
587 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
588 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
589 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
590 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
591 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
592 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::charset-normalizer:3.1.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
593 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::colorama:0.4.6 | DETECTED: BSD-3-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::colorama:0.4.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
594 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: GPL-3.0-only |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license GPL-3.0-only of its dependency 'PyPI::conan:1.58.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
595 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DECLARED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::conan:1.58.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
596 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::conan:1.58.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
597 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::conan:1.58.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
598 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::conan:1.58.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
599 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::conan:1.58.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
600 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::conan:1.58.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
601 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::conan:1.58.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
602 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::conan:1.58.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
603 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::conan:1.58.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
604 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::conan:1.58.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
605 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::conan:1.58.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
606 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::conan:1.58.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
607 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::conan:1.58.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
608 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::conan:1.58.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
609 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::conan:1.58.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
610 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: OpenSSL |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license OpenSSL of its dependency 'PyPI::conan:1.58.0'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
611 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: OpenSSL |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license OpenSSL of its dependency 'PyPI::conan:1.58.0'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
612 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: OpenSSL |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license OpenSSL of its dependency 'PyPI::conan:1.58.0'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
613 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: OpenSSL |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license OpenSSL of its dependency 'PyPI::conan:1.58.0'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
614 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: OpenSSL |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license OpenSSL of its dependency 'PyPI::conan:1.58.0'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
615 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: OpenSSL |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license OpenSSL of its dependency 'PyPI::conan:1.58.0'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
616 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: OpenSSL |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license OpenSSL of its dependency 'PyPI::conan:1.58.0'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
617 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: OpenSSL |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license OpenSSL of its dependency 'PyPI::conan:1.58.0'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
618 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: OpenSSL |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license OpenSSL of its dependency 'PyPI::conan:1.58.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
619 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: OpenSSL |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license OpenSSL of its dependency 'PyPI::conan:1.58.0'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
620 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: OpenSSL |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license OpenSSL of its dependency 'PyPI::conan:1.58.0'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
621 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: OpenSSL |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license OpenSSL of its dependency 'PyPI::conan:1.58.0'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
622 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::conan:1.58.0 | DETECTED: Unlicense |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Unlicense of its dependency 'PyPI::conan:1.58.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
623 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DECLARED: BSD-3-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
624 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: BSD-3-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
625 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: BSL-1.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSL-1.0 of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
626 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: GPL-2.0-only |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license GPL-2.0-only of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
627 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: LGPL-2.1-or-later |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
628 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DECLARED: LicenseRef-scancode-free-unknown |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-free-unknown of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
629 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DECLARED: LicenseRef-scancode-free-unknown |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-free-unknown of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
630 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DECLARED: LicenseRef-scancode-free-unknown |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-free-unknown of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
631 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DECLARED: LicenseRef-scancode-free-unknown |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-free-unknown of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
632 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DECLARED: LicenseRef-scancode-free-unknown |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-free-unknown of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
633 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DECLARED: LicenseRef-scancode-free-unknown |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-free-unknown of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
634 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DECLARED: LicenseRef-scancode-free-unknown |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-free-unknown of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
635 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DECLARED: LicenseRef-scancode-free-unknown |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-free-unknown of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
636 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DECLARED: LicenseRef-scancode-free-unknown |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-free-unknown of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
637 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DECLARED: LicenseRef-scancode-free-unknown |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-free-unknown of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
638 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DECLARED: LicenseRef-scancode-free-unknown |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-free-unknown of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
639 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DECLARED: LicenseRef-scancode-free-unknown |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-free-unknown of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
640 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DECLARED: LicenseRef-scancode-free-unknown |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-free-unknown of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
641 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: LicenseRef-scancode-protobuf |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-protobuf of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
642 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: LicenseRef-scancode-protobuf |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-protobuf of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
643 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: LicenseRef-scancode-protobuf |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-protobuf of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
644 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: LicenseRef-scancode-protobuf |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-protobuf of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
645 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: LicenseRef-scancode-protobuf |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-protobuf of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
646 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: LicenseRef-scancode-protobuf |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-protobuf of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
647 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: LicenseRef-scancode-protobuf |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-protobuf of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
648 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: LicenseRef-scancode-protobuf |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-protobuf of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
649 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: LicenseRef-scancode-protobuf |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-protobuf of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
650 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: LicenseRef-scancode-protobuf |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-protobuf of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
651 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: LicenseRef-scancode-protobuf |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-protobuf of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
652 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: LicenseRef-scancode-protobuf |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-protobuf of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
653 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: LicenseRef-scancode-protobuf |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-protobuf of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
654 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
655 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
656 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
657 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
658 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
659 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: NOASSERTION |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
660 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
661 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
662 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: NOASSERTION |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
663 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: NOASSERTION |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
664 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
665 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
666 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::cpplint:1.6.1 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::cpplint:1.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
667 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: BSD-2-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-2-Clause of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
668 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: BSD-3-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
669 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: HPND |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license HPND of its dependency 'PyPI::distlib:0.3.6'. There is insufficient information or knowledge whether the HPND license is compatible with the EPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the HPND license with the EPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
670 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: HPND |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license HPND of its dependency 'PyPI::distlib:0.3.6'. There is insufficient information or knowledge whether the HPND license is compatible with the EPL-2.0 license or not. Therefore, a general recommendation on the compatibility of the HPND license with the EPL-2.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
671 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: HPND |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license HPND of its dependency 'PyPI::distlib:0.3.6'. There is insufficient information or knowledge whether the HPND license is compatible with the MPL-2.0 license or not. Therefore, a general recommendation on the compatibility of the HPND license with the MPL-2.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
672 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: HPND |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license HPND of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
673 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: HPND |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license HPND of its dependency 'PyPI::distlib:0.3.6'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
674 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
675 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
676 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
677 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
678 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
679 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
680 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: NOASSERTION |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
681 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
682 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
683 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: NOASSERTION |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
684 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: NOASSERTION |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
685 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
686 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
687 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
688 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DECLARED: PSF-2.0 |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license PSF-2.0 of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
689 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DECLARED: PSF-2.0 |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license PSF-2.0 of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
690 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DECLARED: PSF-2.0 |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license PSF-2.0 of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
691 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DECLARED: PSF-2.0 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license PSF-2.0 of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
692 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DECLARED: PSF-2.0 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license PSF-2.0 of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
693 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DECLARED: PSF-2.0 |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license PSF-2.0 of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
694 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DECLARED: PSF-2.0 |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license PSF-2.0 of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
695 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DECLARED: PSF-2.0 |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license PSF-2.0 of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
696 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DECLARED: PSF-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license PSF-2.0 of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
697 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DECLARED: PSF-2.0 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license PSF-2.0 of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
698 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DECLARED: PSF-2.0 |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license PSF-2.0 of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
699 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DECLARED: PSF-2.0 |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license PSF-2.0 of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
700 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DECLARED: PSF-2.0 |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license PSF-2.0 of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
701 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: Python-2.0 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::distlib:0.3.6'. There is insufficient information or knowledge whether the Python-2.0 license is compatible with the EPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the EPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
702 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: Python-2.0 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::distlib:0.3.6'. There is insufficient information or knowledge whether the Python-2.0 license is compatible with the EPL-2.0 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the EPL-2.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
703 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: Python-2.0 |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::distlib:0.3.6'. There is insufficient information or knowledge whether the Python-2.0 license is compatible with the MPL-2.0 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the MPL-2.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
704 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: Python-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
705 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: Python-2.0 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::distlib:0.3.6'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
706 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
707 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
708 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
709 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
710 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
711 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
712 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
713 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
714 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
715 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
716 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
717 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
718 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distlib:0.3.6 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::distlib:0.3.6'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
719 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distro:1.7.0 | DECLARED: Apache-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::distro:1.7.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
720 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distro:1.7.0 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::distro:1.7.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
721 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distro:1.7.0 | DECLARED: Apache-2.0 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::distro:1.7.0'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
722 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::distro:1.7.0 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::distro:1.7.0'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
723 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::fasteners:0.18 | DECLARED: Apache-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::fasteners:0.18'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
724 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::fasteners:0.18 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::fasteners:0.18'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
725 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::fasteners:0.18 | DECLARED: Apache-2.0 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::fasteners:0.18'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
726 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::fasteners:0.18 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::fasteners:0.18'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
727 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::filelock:3.10.7 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::filelock:3.10.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
728 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::filelock:3.10.7 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::filelock:3.10.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
729 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::filelock:3.10.7 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::filelock:3.10.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
730 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::filelock:3.10.7 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::filelock:3.10.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
731 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::filelock:3.10.7 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::filelock:3.10.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
732 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::filelock:3.10.7 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::filelock:3.10.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
733 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::filelock:3.10.7 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::filelock:3.10.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
734 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::filelock:3.10.7 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::filelock:3.10.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
735 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::filelock:3.10.7 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::filelock:3.10.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
736 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::filelock:3.10.7 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::filelock:3.10.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
737 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::filelock:3.10.7 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::filelock:3.10.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
738 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::filelock:3.10.7 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::filelock:3.10.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
739 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::filelock:3.10.7 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::filelock:3.10.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
740 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::filelock:3.10.7 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::filelock:3.10.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
741 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::filelock:3.10.7 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::filelock:3.10.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
742 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::filelock:3.10.7 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::filelock:3.10.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
743 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::filelock:3.10.7 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::filelock:3.10.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
744 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::filelock:3.10.7 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::filelock:3.10.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
745 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::filelock:3.10.7 | DETECTED: NOASSERTION |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::filelock:3.10.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
746 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::filelock:3.10.7 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::filelock:3.10.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
747 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::filelock:3.10.7 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::filelock:3.10.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
748 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::filelock:3.10.7 | DETECTED: NOASSERTION |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::filelock:3.10.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
749 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::filelock:3.10.7 | DETECTED: NOASSERTION |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::filelock:3.10.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
750 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::filelock:3.10.7 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::filelock:3.10.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
751 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::filelock:3.10.7 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::filelock:3.10.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
752 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::filelock:3.10.7 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::filelock:3.10.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
753 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::filelock:3.10.7 | DETECTED: Unlicense |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Unlicense of its dependency 'PyPI::filelock:3.10.7'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
754 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::gcovr:5.2 | DECLARED: BSD-3-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::gcovr:5.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
755 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::gcovr:5.2 | DETECTED: BSD-3-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::gcovr:5.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
756 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::gcovr:5.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::gcovr:5.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
757 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::gcovr:5.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::gcovr:5.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
758 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::gcovr:5.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::gcovr:5.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
759 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::gcovr:5.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::gcovr:5.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
760 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::gcovr:5.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::gcovr:5.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
761 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::gcovr:5.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::gcovr:5.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
762 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::gcovr:5.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::gcovr:5.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
763 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::gcovr:5.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::gcovr:5.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
764 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::gcovr:5.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::gcovr:5.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
765 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::gcovr:5.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::gcovr:5.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
766 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::gcovr:5.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::gcovr:5.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
767 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::gcovr:5.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::gcovr:5.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
768 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::gcovr:5.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::gcovr:5.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
769 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: 0BSD |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license 0BSD of its dependency 'PyPI::identify:2.5.22'. There is insufficient information or knowledge whether the 0BSD license is compatible with the EPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the 0BSD license with the EPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
770 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: 0BSD |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license 0BSD of its dependency 'PyPI::identify:2.5.22'. There is insufficient information or knowledge whether the 0BSD license is compatible with the EPL-2.0 license or not. Therefore, a general recommendation on the compatibility of the 0BSD license with the EPL-2.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
771 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: 0BSD |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license 0BSD of its dependency 'PyPI::identify:2.5.22'. There is insufficient information or knowledge whether the 0BSD license is compatible with the MPL-2.0 license or not. Therefore, a general recommendation on the compatibility of the 0BSD license with the MPL-2.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
772 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: 0BSD |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license 0BSD of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
773 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: 0BSD |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license 0BSD of its dependency 'PyPI::identify:2.5.22'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
774 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: AFL-3.0 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license AFL-3.0 of its dependency 'PyPI::identify:2.5.22'. There is insufficient information or knowledge whether the AFL-3.0 license is compatible with the EPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the AFL-3.0 license with the EPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
775 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: AFL-3.0 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license AFL-3.0 of its dependency 'PyPI::identify:2.5.22'. There is insufficient information or knowledge whether the AFL-3.0 license is compatible with the EPL-2.0 license or not. Therefore, a general recommendation on the compatibility of the AFL-3.0 license with the EPL-2.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
776 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: AFL-3.0 |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license AFL-3.0 of its dependency 'PyPI::identify:2.5.22'. There is insufficient information or knowledge whether the AFL-3.0 license is compatible with the MPL-2.0 license or not. Therefore, a general recommendation on the compatibility of the AFL-3.0 license with the MPL-2.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
777 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: AFL-3.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license AFL-3.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
778 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: AFL-3.0 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license AFL-3.0 of its dependency 'PyPI::identify:2.5.22'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
779 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: AGPL-3.0-only |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license AGPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
780 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
781 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::identify:2.5.22'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
782 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: Artistic-2.0 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Artistic-2.0 of its dependency 'PyPI::identify:2.5.22'. There is insufficient information or knowledge whether the Artistic-2.0 license is compatible with the EPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Artistic-2.0 license with the EPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
783 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: Artistic-2.0 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Artistic-2.0 of its dependency 'PyPI::identify:2.5.22'. There is insufficient information or knowledge whether the Artistic-2.0 license is compatible with the EPL-2.0 license or not. Therefore, a general recommendation on the compatibility of the Artistic-2.0 license with the EPL-2.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
784 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: Artistic-2.0 |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Artistic-2.0 of its dependency 'PyPI::identify:2.5.22'. There is insufficient information or knowledge whether the Artistic-2.0 license is compatible with the MPL-2.0 license or not. Therefore, a general recommendation on the compatibility of the Artistic-2.0 license with the MPL-2.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
785 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: Artistic-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Artistic-2.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
786 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: Artistic-2.0 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Artistic-2.0 of its dependency 'PyPI::identify:2.5.22'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
787 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: BSD-2-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-2-Clause of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
788 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: BSD-3-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
789 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: BSD-3-Clause-Clear |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause-Clear of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
790 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: BSD-3-Clause-Clear |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause-Clear of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
791 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: BSD-3-Clause-Clear |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause-Clear of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
792 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: BSD-3-Clause-Clear |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause-Clear of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
793 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: BSD-3-Clause-Clear |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause-Clear of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
794 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: BSD-3-Clause-Clear |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause-Clear of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
795 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: BSD-3-Clause-Clear |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause-Clear of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
796 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: BSD-3-Clause-Clear |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause-Clear of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
797 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: BSD-3-Clause-Clear |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause-Clear of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
798 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: BSD-3-Clause-Clear |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause-Clear of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
799 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: BSD-3-Clause-Clear |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause-Clear of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
800 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: BSD-3-Clause-Clear |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause-Clear of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
801 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: BSD-3-Clause-Clear |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause-Clear of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
802 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: BSL-1.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSL-1.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
803 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
804 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
805 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
806 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
807 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
808 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
809 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
810 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
811 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
812 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
813 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
814 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
815 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
816 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: CC-BY-SA-4.0 |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-SA-4.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
817 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: CC-BY-SA-4.0 |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-SA-4.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
818 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: CC-BY-SA-4.0 |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-SA-4.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
819 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: CC-BY-SA-4.0 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-SA-4.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
820 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: CC-BY-SA-4.0 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-SA-4.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
821 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: CC-BY-SA-4.0 |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-SA-4.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
822 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: CC-BY-SA-4.0 |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-SA-4.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
823 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: CC-BY-SA-4.0 |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-SA-4.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
824 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: CC-BY-SA-4.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-SA-4.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
825 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: CC-BY-SA-4.0 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-SA-4.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
826 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: CC-BY-SA-4.0 |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-SA-4.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
827 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: CC-BY-SA-4.0 |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-SA-4.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
828 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: CC-BY-SA-4.0 |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC-BY-SA-4.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
829 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: CC0-1.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CC0-1.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
830 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: ECL-2.0 |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license ECL-2.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
831 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: ECL-2.0 |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license ECL-2.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
832 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: ECL-2.0 |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license ECL-2.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
833 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: ECL-2.0 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license ECL-2.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
834 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: ECL-2.0 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license ECL-2.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
835 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: ECL-2.0 |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license ECL-2.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
836 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: ECL-2.0 |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license ECL-2.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
837 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: ECL-2.0 |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license ECL-2.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
838 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: ECL-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license ECL-2.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
839 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: ECL-2.0 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license ECL-2.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
840 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: ECL-2.0 |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license ECL-2.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
841 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: ECL-2.0 |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license ECL-2.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
842 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: ECL-2.0 |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license ECL-2.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
843 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EPL-1.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license EPL-1.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
844 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EPL-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license EPL-2.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
845 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EUPL-1.1 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license EUPL-1.1 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
846 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: EUPL-1.2 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license EUPL-1.2 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
847 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-1.0-or-later |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
848 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-2.0-only |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license GPL-2.0-only of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
849 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: GPL-3.0-only |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license GPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
850 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: ISC |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license ISC of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
851 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LGPL-2.1-only |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
852 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LGPL-3.0-only |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-3.0-only of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
853 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LPPL-1.3c |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LPPL-1.3c of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
854 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LPPL-1.3c |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LPPL-1.3c of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
855 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LPPL-1.3c |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LPPL-1.3c of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
856 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LPPL-1.3c |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LPPL-1.3c of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
857 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LPPL-1.3c |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LPPL-1.3c of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
858 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LPPL-1.3c |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LPPL-1.3c of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
859 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LPPL-1.3c |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LPPL-1.3c of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
860 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LPPL-1.3c |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LPPL-1.3c of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
861 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LPPL-1.3c |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LPPL-1.3c of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
862 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LPPL-1.3c |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LPPL-1.3c of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
863 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LPPL-1.3c |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LPPL-1.3c of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
864 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LPPL-1.3c |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LPPL-1.3c of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
865 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: LPPL-1.3c |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LPPL-1.3c of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
866 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DECLARED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
867 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
868 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MPL-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MPL-2.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
869 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MS-PL |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MS-PL of its dependency 'PyPI::identify:2.5.22'. It is unclear whether "any portion of the software" assumes code changes and additions that also must be distributed "only under this license". In addition, a "license that complies with this license" may or may not be interpreted as a copyleft clause. If not, the copyleft condition would depend on the mode of delivery which would require a case-by-case assessment. Therefore, a general recommendation on the compatibility of the MS-PL license can only be given for selected cases. Interpretation: It is unclear whether "any portion of the software" assumes code changes and additions that also must be distributed "only under this license". In addition, a "license that complies with this license" may or may not be interpreted as a copyleft clause. If not, the copyleft condition would depend on the mode of delivery which would require a case-by-case assessment. Therefore, a general recommendation on the compatibility of the MS-PL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
870 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MS-PL |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MS-PL of its dependency 'PyPI::identify:2.5.22'. It is unclear whether "any portion of the software" assumes code changes and additions that also must be distributed "only under this license". In addition, a "license that complies with this license" may or may not be interpreted as a copyleft clause. If not, the copyleft condition would depend on the mode of delivery which would require a case-by-case assessment. Therefore, a general recommendation on the compatibility of the MS-PL license can only be given for selected cases. Interpretation: It is unclear whether "any portion of the software" assumes code changes and additions that also must be distributed "only under this license". In addition, a "license that complies with this license" may or may not be interpreted as a copyleft clause. If not, the copyleft condition would depend on the mode of delivery which would require a case-by-case assessment. Therefore, a general recommendation on the compatibility of the MS-PL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
871 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MS-PL |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MS-PL of its dependency 'PyPI::identify:2.5.22'. It is unclear whether "any portion of the software" assumes code changes and additions that also must be distributed "only under this license". In addition, a "license that complies with this license" may or may not be interpreted as a copyleft clause. If not, the copyleft condition would depend on the mode of delivery which would require a case-by-case assessment. Therefore, a general recommendation on the compatibility of the MS-PL license can only be given for selected cases. Interpretation: It is unclear whether "any portion of the software" assumes code changes and additions that also must be distributed "only under this license". In addition, a "license that complies with this license" may or may not be interpreted as a copyleft clause. If not, the copyleft condition would depend on the mode of delivery which would require a case-by-case assessment. Therefore, a general recommendation on the compatibility of the MS-PL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
872 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MS-PL |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MS-PL of its dependency 'PyPI::identify:2.5.22'. It is unclear whether "any portion of the software" assumes code changes and additions that also must be distributed "only under this license". In addition, a "license that complies with this license" may or may not be interpreted as a copyleft clause. If not, the copyleft condition would depend on the mode of delivery which would require a case-by-case assessment. Therefore, a general recommendation on the compatibility of the MS-PL license can only be given for selected cases. Interpretation: It is unclear whether "any portion of the software" assumes code changes and additions that also must be distributed "only under this license". In addition, a "license that complies with this license" may or may not be interpreted as a copyleft clause. If not, the copyleft condition would depend on the mode of delivery which would require a case-by-case assessment. Therefore, a general recommendation on the compatibility of the MS-PL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
873 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MS-PL |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MS-PL of its dependency 'PyPI::identify:2.5.22'. It is unclear whether "any portion of the software" assumes code changes and additions that also must be distributed "only under this license". In addition, a "license that complies with this license" may or may not be interpreted as a copyleft clause. If not, the copyleft condition would depend on the mode of delivery which would require a case-by-case assessment. Therefore, a general recommendation on the compatibility of the MS-PL license can only be given for selected cases. Interpretation: It is unclear whether "any portion of the software" assumes code changes and additions that also must be distributed "only under this license". In addition, a "license that complies with this license" may or may not be interpreted as a copyleft clause. If not, the copyleft condition would depend on the mode of delivery which would require a case-by-case assessment. Therefore, a general recommendation on the compatibility of the MS-PL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
874 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MS-PL |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MS-PL of its dependency 'PyPI::identify:2.5.22'. It is unclear whether "any portion of the software" assumes code changes and additions that also must be distributed "only under this license". In addition, a "license that complies with this license" may or may not be interpreted as a copyleft clause. If not, the copyleft condition would depend on the mode of delivery which would require a case-by-case assessment. Therefore, a general recommendation on the compatibility of the MS-PL license can only be given for selected cases. Interpretation: It is unclear whether "any portion of the software" assumes code changes and additions that also must be distributed "only under this license". In addition, a "license that complies with this license" may or may not be interpreted as a copyleft clause. If not, the copyleft condition would depend on the mode of delivery which would require a case-by-case assessment. Therefore, a general recommendation on the compatibility of the MS-PL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
875 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MS-PL |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MS-PL of its dependency 'PyPI::identify:2.5.22'. It is unclear whether "any portion of the software" assumes code changes and additions that also must be distributed "only under this license". In addition, a "license that complies with this license" may or may not be interpreted as a copyleft clause. If not, the copyleft condition would depend on the mode of delivery which would require a case-by-case assessment. Therefore, a general recommendation on the compatibility of the MS-PL license can only be given for selected cases. Interpretation: It is unclear whether "any portion of the software" assumes code changes and additions that also must be distributed "only under this license". In addition, a "license that complies with this license" may or may not be interpreted as a copyleft clause. If not, the copyleft condition would depend on the mode of delivery which would require a case-by-case assessment. Therefore, a general recommendation on the compatibility of the MS-PL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
876 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MS-PL |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MS-PL of its dependency 'PyPI::identify:2.5.22'. It is unclear whether "any portion of the software" assumes code changes and additions that also must be distributed "only under this license". In addition, a "license that complies with this license" may or may not be interpreted as a copyleft clause. If not, the copyleft condition would depend on the mode of delivery which would require a case-by-case assessment. Therefore, a general recommendation on the compatibility of the MS-PL license can only be given for selected cases. Interpretation: It is unclear whether "any portion of the software" assumes code changes and additions that also must be distributed "only under this license". In addition, a "license that complies with this license" may or may not be interpreted as a copyleft clause. If not, the copyleft condition would depend on the mode of delivery which would require a case-by-case assessment. Therefore, a general recommendation on the compatibility of the MS-PL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
877 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MS-PL |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MS-PL of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
878 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MS-PL |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MS-PL of its dependency 'PyPI::identify:2.5.22'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
879 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MS-PL |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MS-PL of its dependency 'PyPI::identify:2.5.22'. It is unclear whether "any portion of the software" assumes code changes and additions that also must be distributed "only under this license". In addition, a "license that complies with this license" may or may not be interpreted as a copyleft clause. If not, the copyleft condition would depend on the mode of delivery which would require a case-by-case assessment. Therefore, a general recommendation on the compatibility of the MS-PL license can only be given for selected cases. Interpretation: It is unclear whether "any portion of the software" assumes code changes and additions that also must be distributed "only under this license". In addition, a "license that complies with this license" may or may not be interpreted as a copyleft clause. If not, the copyleft condition would depend on the mode of delivery which would require a case-by-case assessment. Therefore, a general recommendation on the compatibility of the MS-PL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
880 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MS-PL |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MS-PL of its dependency 'PyPI::identify:2.5.22'. It is unclear whether "any portion of the software" assumes code changes and additions that also must be distributed "only under this license". In addition, a "license that complies with this license" may or may not be interpreted as a copyleft clause. If not, the copyleft condition would depend on the mode of delivery which would require a case-by-case assessment. Therefore, a general recommendation on the compatibility of the MS-PL license can only be given for selected cases. Interpretation: It is unclear whether "any portion of the software" assumes code changes and additions that also must be distributed "only under this license". In addition, a "license that complies with this license" may or may not be interpreted as a copyleft clause. If not, the copyleft condition would depend on the mode of delivery which would require a case-by-case assessment. Therefore, a general recommendation on the compatibility of the MS-PL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
881 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MS-PL |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MS-PL of its dependency 'PyPI::identify:2.5.22'. It is unclear whether "any portion of the software" assumes code changes and additions that also must be distributed "only under this license". In addition, a "license that complies with this license" may or may not be interpreted as a copyleft clause. If not, the copyleft condition would depend on the mode of delivery which would require a case-by-case assessment. Therefore, a general recommendation on the compatibility of the MS-PL license can only be given for selected cases. Interpretation: It is unclear whether "any portion of the software" assumes code changes and additions that also must be distributed "only under this license". In addition, a "license that complies with this license" may or may not be interpreted as a copyleft clause. If not, the copyleft condition would depend on the mode of delivery which would require a case-by-case assessment. Therefore, a general recommendation on the compatibility of the MS-PL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
882 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: MS-RL |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MS-RL of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
883 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: NCSA |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NCSA of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
884 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: NCSA |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NCSA of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
885 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: NCSA |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NCSA of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
886 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: NCSA |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NCSA of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
887 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: NCSA |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NCSA of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
888 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: NCSA |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NCSA of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
889 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: NCSA |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NCSA of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
890 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: NCSA |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NCSA of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
891 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: NCSA |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NCSA of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
892 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: NCSA |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NCSA of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
893 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: NCSA |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NCSA of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
894 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: NCSA |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NCSA of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
895 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: NCSA |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NCSA of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
896 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
897 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
898 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
899 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
900 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
901 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: NOASSERTION |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
902 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
903 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
904 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: NOASSERTION |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
905 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: NOASSERTION |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
906 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
907 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
908 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
909 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: OFL-1.1 |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license OFL-1.1 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
910 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: OFL-1.1 |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license OFL-1.1 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
911 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: OFL-1.1 |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license OFL-1.1 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
912 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: OFL-1.1 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license OFL-1.1 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
913 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: OFL-1.1 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license OFL-1.1 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
914 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: OFL-1.1 |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license OFL-1.1 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
915 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: OFL-1.1 |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license OFL-1.1 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
916 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: OFL-1.1 |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license OFL-1.1 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
917 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: OFL-1.1 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license OFL-1.1 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
918 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: OFL-1.1 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license OFL-1.1 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
919 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: OFL-1.1 |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license OFL-1.1 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
920 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: OFL-1.1 |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license OFL-1.1 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
921 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: OFL-1.1 |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license OFL-1.1 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
922 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: OSL-3.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license OSL-3.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
923 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: PostgreSQL |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license PostgreSQL of its dependency 'PyPI::identify:2.5.22'. There is insufficient information or knowledge whether the PostgreSQL license is compatible with the EPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the PostgreSQL license with the EPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
924 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: PostgreSQL |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license PostgreSQL of its dependency 'PyPI::identify:2.5.22'. There is insufficient information or knowledge whether the PostgreSQL license is compatible with the EPL-2.0 license or not. Therefore, a general recommendation on the compatibility of the PostgreSQL license with the EPL-2.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
925 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: PostgreSQL |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license PostgreSQL of its dependency 'PyPI::identify:2.5.22'. There is insufficient information or knowledge whether the PostgreSQL license is compatible with the MPL-2.0 license or not. Therefore, a general recommendation on the compatibility of the PostgreSQL license with the MPL-2.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
926 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: PostgreSQL |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license PostgreSQL of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
927 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: PostgreSQL |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license PostgreSQL of its dependency 'PyPI::identify:2.5.22'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
928 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: UPL-1.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license UPL-1.0 of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
929 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: Unlicense |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Unlicense of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
930 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: WTFPL |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license WTFPL of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
931 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::identify:2.5.22 | DETECTED: Zlib |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Zlib of its dependency 'PyPI::identify:2.5.22'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
932 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::idna:3.4 | DETECTED: BSD-3-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::idna:3.4'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
933 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::idna:3.4 | DETECTED: LicenseRef-scancode-unicode |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-unicode of its dependency 'PyPI::idna:3.4'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
934 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::idna:3.4 | DETECTED: LicenseRef-scancode-unicode |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-unicode of its dependency 'PyPI::idna:3.4'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
935 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::idna:3.4 | DETECTED: LicenseRef-scancode-unicode |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-unicode of its dependency 'PyPI::idna:3.4'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
936 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::idna:3.4 | DETECTED: LicenseRef-scancode-unicode |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-unicode of its dependency 'PyPI::idna:3.4'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
937 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::idna:3.4 | DETECTED: LicenseRef-scancode-unicode |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-unicode of its dependency 'PyPI::idna:3.4'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
938 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::idna:3.4 | DETECTED: LicenseRef-scancode-unicode |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-unicode of its dependency 'PyPI::idna:3.4'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
939 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::idna:3.4 | DETECTED: LicenseRef-scancode-unicode |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-unicode of its dependency 'PyPI::idna:3.4'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
940 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::idna:3.4 | DETECTED: LicenseRef-scancode-unicode |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-unicode of its dependency 'PyPI::idna:3.4'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
941 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::idna:3.4 | DETECTED: LicenseRef-scancode-unicode |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-unicode of its dependency 'PyPI::idna:3.4'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
942 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::idna:3.4 | DETECTED: LicenseRef-scancode-unicode |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-unicode of its dependency 'PyPI::idna:3.4'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
943 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::idna:3.4 | DETECTED: LicenseRef-scancode-unicode |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-unicode of its dependency 'PyPI::idna:3.4'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
944 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::idna:3.4 | DETECTED: LicenseRef-scancode-unicode |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-unicode of its dependency 'PyPI::idna:3.4'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
945 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::idna:3.4 | DETECTED: LicenseRef-scancode-unicode |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-unicode of its dependency 'PyPI::idna:3.4'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
946 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::jinja2:3.1.2 | DETECTED: BSD-2-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-2-Clause of its dependency 'PyPI::jinja2:3.1.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
947 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::jinja2:3.1.2 | DECLARED: BSD-3-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::jinja2:3.1.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
948 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::jinja2:3.1.2 | DETECTED: BSD-3-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::jinja2:3.1.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
949 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::jinja2:3.1.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::jinja2:3.1.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
950 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::jinja2:3.1.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::jinja2:3.1.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
951 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::jinja2:3.1.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::jinja2:3.1.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
952 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::jinja2:3.1.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::jinja2:3.1.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
953 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::jinja2:3.1.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::jinja2:3.1.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
954 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::jinja2:3.1.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::jinja2:3.1.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
955 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::jinja2:3.1.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::jinja2:3.1.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
956 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::jinja2:3.1.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::jinja2:3.1.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
957 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::jinja2:3.1.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::jinja2:3.1.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
958 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::jinja2:3.1.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::jinja2:3.1.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
959 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::jinja2:3.1.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::jinja2:3.1.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
960 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::jinja2:3.1.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::jinja2:3.1.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
961 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::jinja2:3.1.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::jinja2:3.1.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
962 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DECLARED: BSD-3-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
963 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: BSD-3-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
964 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-1.0-or-later |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
965 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-2.0-only |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license GPL-2.0-only of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
966 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: GPL-2.0-or-later |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
967 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
968 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
969 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
970 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
971 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
972 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
973 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
974 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
975 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
976 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
977 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
978 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
979 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
980 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
981 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
982 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
983 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
984 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
985 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
986 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
987 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
988 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
989 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
990 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
991 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
992 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
993 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-secret-labs-2011 |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-secret-labs-2011 of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
994 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-secret-labs-2011 |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-secret-labs-2011 of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
995 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-secret-labs-2011 |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-secret-labs-2011 of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
996 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-secret-labs-2011 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-secret-labs-2011 of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
997 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-secret-labs-2011 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-secret-labs-2011 of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
998 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-secret-labs-2011 |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-secret-labs-2011 of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
999 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-secret-labs-2011 |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-secret-labs-2011 of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1000 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-secret-labs-2011 |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-secret-labs-2011 of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1001 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-secret-labs-2011 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-secret-labs-2011 of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1002 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-secret-labs-2011 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-secret-labs-2011 of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1003 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-secret-labs-2011 |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-secret-labs-2011 of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1004 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-secret-labs-2011 |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-secret-labs-2011 of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1005 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-secret-labs-2011 |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-secret-labs-2011 of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1006 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1007 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1008 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1009 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1010 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1011 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1012 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1013 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1014 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1015 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1016 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1017 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1018 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1019 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1020 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lxml:4.9.2 | DETECTED: Zlib |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Zlib of its dependency 'PyPI::lxml:4.9.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1021 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::markupsafe:2.1.2 | DETECTED: BSD-2-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-2-Clause of its dependency 'PyPI::markupsafe:2.1.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1022 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::markupsafe:2.1.2 | DECLARED: BSD-3-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::markupsafe:2.1.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1023 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::markupsafe:2.1.2 | DETECTED: BSD-3-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::markupsafe:2.1.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1024 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::node-semver:0.6.1 | DECLARED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::node-semver:0.6.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1025 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::nodeenv:1.7.0 | DECLARED: BSD-3-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::nodeenv:1.7.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1026 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::nodeenv:1.7.0 | DETECTED: BSD-3-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::nodeenv:1.7.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1027 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::patch-ng:1.17.4'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1028 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::patch-ng:1.17.4'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1029 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: BSD-3-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::patch-ng:1.17.4'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1030 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: GPL-1.0-or-later |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::patch-ng:1.17.4'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1031 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: GPL-3.0-only |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license GPL-3.0-only of its dependency 'PyPI::patch-ng:1.17.4'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1032 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DECLARED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::patch-ng:1.17.4'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1033 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::patch-ng:1.17.4 | DETECTED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::patch-ng:1.17.4'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1034 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::platformdirs:3.2.0 | DECLARED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::platformdirs:3.2.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1035 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::platformdirs:3.2.0 | DETECTED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::platformdirs:3.2.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1036 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pluginbase:1.0.1 | DETECTED: BSD-2-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-2-Clause of its dependency 'PyPI::pluginbase:1.0.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1037 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pluginbase:1.0.1 | DETECTED: BSD-3-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::pluginbase:1.0.1'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1038 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pre-commit:2.20.0 | DETECTED: GPL-3.0-only |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license GPL-3.0-only of its dependency 'PyPI::pre-commit:2.20.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1039 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pre-commit:2.20.0 | DECLARED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::pre-commit:2.20.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1040 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pre-commit:2.20.0 | DETECTED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::pre-commit:2.20.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1041 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: AFL-3.0 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license AFL-3.0 of its dependency 'PyPI::pygments:2.14.0'. There is insufficient information or knowledge whether the AFL-3.0 license is compatible with the EPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the AFL-3.0 license with the EPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1042 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: AFL-3.0 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license AFL-3.0 of its dependency 'PyPI::pygments:2.14.0'. There is insufficient information or knowledge whether the AFL-3.0 license is compatible with the EPL-2.0 license or not. Therefore, a general recommendation on the compatibility of the AFL-3.0 license with the EPL-2.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1043 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: AFL-3.0 |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license AFL-3.0 of its dependency 'PyPI::pygments:2.14.0'. There is insufficient information or knowledge whether the AFL-3.0 license is compatible with the MPL-2.0 license or not. Therefore, a general recommendation on the compatibility of the AFL-3.0 license with the MPL-2.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1044 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: AFL-3.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license AFL-3.0 of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1045 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: AFL-3.0 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license AFL-3.0 of its dependency 'PyPI::pygments:2.14.0'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1046 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1047 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::pygments:2.14.0'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1048 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: Apache-2.0 WITH LLVM-exception |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 (simplified from 'Apache-2.0 WITH LLVM-exception') of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1049 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: Apache-2.0 WITH LLVM-exception |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 (simplified from 'Apache-2.0 WITH LLVM-exception') of its dependency 'PyPI::pygments:2.14.0'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1050 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DECLARED: BSD-2-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-2-Clause of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1051 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: BSD-2-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-2-Clause of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1052 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: BSD-3-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1053 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: BSL-1.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSL-1.0 of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1054 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: CPL-1.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license CPL-1.0 of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1055 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-1.0-or-later |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1056 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-only |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1057 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1058 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1059 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1060 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license GPL-2.0-or-later (simplified from 'GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0') of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1061 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-3.0-only |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license GPL-3.0-only of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1062 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: GPL-3.0-or-later |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license GPL-3.0-or-later of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1063 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1064 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1065 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1066 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1067 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1068 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1069 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1070 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1071 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1072 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1073 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1074 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1075 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1076 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later (simplified from 'LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception') of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1077 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later (simplified from 'LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception') of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1078 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later (simplified from 'LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception') of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1079 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later (simplified from 'LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception') of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1080 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later (simplified from 'LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception') of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1081 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later (simplified from 'LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception') of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1082 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later (simplified from 'LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception') of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1083 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later (simplified from 'LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception') of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1084 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later (simplified from 'LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception') of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1085 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later (simplified from 'LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception') of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1086 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later (simplified from 'LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception') of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1087 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later (simplified from 'LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception') of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1088 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later (simplified from 'LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception') of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1089 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-only |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1090 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-only WITH Qt-LGPL-exception-1.1 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.1-only (simplified from 'LGPL-2.1-only WITH Qt-LGPL-exception-1.1') of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1091 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-or-later |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1092 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LGPL-3.0-only |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-3.0-only of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1093 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-commercial-license |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-commercial-license of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1094 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-commercial-license |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-commercial-license of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1095 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-commercial-license |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-commercial-license of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1096 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-commercial-license |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-commercial-license of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1097 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-commercial-license |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-commercial-license of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1098 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-commercial-license |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-commercial-license of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1099 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-commercial-license |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-commercial-license of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1100 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-commercial-license |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-commercial-license of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1101 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-commercial-license |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-commercial-license of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1102 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-commercial-license |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-commercial-license of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1103 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-commercial-license |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-commercial-license of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1104 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-commercial-license |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-commercial-license of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1105 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-commercial-license |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-commercial-license of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1106 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-iso-8879 |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-iso-8879 of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1107 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-iso-8879 |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-iso-8879 of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1108 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-iso-8879 |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-iso-8879 of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1109 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-iso-8879 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-iso-8879 of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1110 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-iso-8879 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-iso-8879 of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1111 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-iso-8879 |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-iso-8879 of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1112 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-iso-8879 |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-iso-8879 of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1113 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-iso-8879 |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-iso-8879 of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1114 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-iso-8879 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-iso-8879 of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1115 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-iso-8879 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-iso-8879 of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1116 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-iso-8879 |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-iso-8879 of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1117 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-iso-8879 |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-iso-8879 of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1118 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-iso-8879 |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-iso-8879 of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1119 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1120 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1121 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1122 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1123 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1124 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1125 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1126 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1127 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1128 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1129 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1130 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1131 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1132 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1133 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1134 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1135 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1136 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1137 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1138 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1139 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1140 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1141 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1142 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1143 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1144 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1145 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-public-domain-disclaimer |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain-disclaimer of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1146 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-public-domain-disclaimer |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain-disclaimer of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1147 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-public-domain-disclaimer |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain-disclaimer of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1148 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-public-domain-disclaimer |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain-disclaimer of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1149 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-public-domain-disclaimer |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain-disclaimer of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1150 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-public-domain-disclaimer |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain-disclaimer of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1151 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-public-domain-disclaimer |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain-disclaimer of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1152 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-public-domain-disclaimer |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain-disclaimer of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1153 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-public-domain-disclaimer |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain-disclaimer of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1154 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-public-domain-disclaimer |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain-disclaimer of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1155 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-public-domain-disclaimer |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain-disclaimer of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1156 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-public-domain-disclaimer |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain-disclaimer of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1157 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-public-domain-disclaimer |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain-disclaimer of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1158 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1159 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MIT-Modern-Variant |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT-Modern-Variant of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1160 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MIT-Modern-Variant |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT-Modern-Variant of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1161 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MIT-Modern-Variant |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT-Modern-Variant of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1162 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MIT-Modern-Variant |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT-Modern-Variant of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1163 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MIT-Modern-Variant |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT-Modern-Variant of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1164 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MIT-Modern-Variant |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT-Modern-Variant of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1165 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MIT-Modern-Variant |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT-Modern-Variant of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1166 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MIT-Modern-Variant |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT-Modern-Variant of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1167 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MIT-Modern-Variant |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT-Modern-Variant of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1168 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MIT-Modern-Variant |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT-Modern-Variant of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1169 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MIT-Modern-Variant |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT-Modern-Variant of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1170 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MIT-Modern-Variant |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT-Modern-Variant of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1171 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MIT-Modern-Variant |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT-Modern-Variant of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1172 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MPL-1.1 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MPL-1.1 of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1173 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: MPL-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MPL-2.0 of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1174 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1175 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1176 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1177 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1178 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1179 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1180 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1181 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1182 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1183 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1184 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1185 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1186 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1187 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: PostgreSQL |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license PostgreSQL of its dependency 'PyPI::pygments:2.14.0'. There is insufficient information or knowledge whether the PostgreSQL license is compatible with the EPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the PostgreSQL license with the EPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1188 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: PostgreSQL |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license PostgreSQL of its dependency 'PyPI::pygments:2.14.0'. There is insufficient information or knowledge whether the PostgreSQL license is compatible with the EPL-2.0 license or not. Therefore, a general recommendation on the compatibility of the PostgreSQL license with the EPL-2.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1189 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: PostgreSQL |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license PostgreSQL of its dependency 'PyPI::pygments:2.14.0'. There is insufficient information or knowledge whether the PostgreSQL license is compatible with the MPL-2.0 license or not. Therefore, a general recommendation on the compatibility of the PostgreSQL license with the MPL-2.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1190 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: PostgreSQL |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license PostgreSQL of its dependency 'PyPI::pygments:2.14.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1191 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pygments:2.14.0 | DETECTED: PostgreSQL |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license PostgreSQL of its dependency 'PyPI::pygments:2.14.0'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1192 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pyjwt:2.6.0 | DECLARED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::pyjwt:2.6.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1193 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pyjwt:2.6.0 | DETECTED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::pyjwt:2.6.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1194 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DECLARED: Apache-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::python-dateutil:2.8.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1195 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::python-dateutil:2.8.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1196 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DECLARED: Apache-2.0 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::python-dateutil:2.8.2'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1197 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::python-dateutil:2.8.2'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1198 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: BSD-2-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-2-Clause of its dependency 'PyPI::python-dateutil:2.8.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1199 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: BSD-3-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::python-dateutil:2.8.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1200 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::python-dateutil:2.8.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1201 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::python-dateutil:2.8.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1202 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::python-dateutil:2.8.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1203 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::python-dateutil:2.8.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1204 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::python-dateutil:2.8.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1205 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::python-dateutil:2.8.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1206 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::python-dateutil:2.8.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1207 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::python-dateutil:2.8.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1208 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::python-dateutil:2.8.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1209 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::python-dateutil:2.8.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1210 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::python-dateutil:2.8.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1211 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::python-dateutil:2.8.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1212 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::python-dateutil:2.8.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1213 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: Python-2.0 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::python-dateutil:2.8.2'. There is insufficient information or knowledge whether the Python-2.0 license is compatible with the EPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the EPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1214 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: Python-2.0 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::python-dateutil:2.8.2'. There is insufficient information or knowledge whether the Python-2.0 license is compatible with the EPL-2.0 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the EPL-2.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1215 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: Python-2.0 |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::python-dateutil:2.8.2'. There is insufficient information or knowledge whether the Python-2.0 license is compatible with the MPL-2.0 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the MPL-2.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1216 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: Python-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::python-dateutil:2.8.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1217 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: Python-2.0 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::python-dateutil:2.8.2'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1218 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pyyaml:6.0 | DECLARED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::pyyaml:6.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1219 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pyyaml:6.0 | DETECTED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::pyyaml:6.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1220 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DECLARED: Apache-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1221 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1222 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DECLARED: Apache-2.0 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::requests:2.28.2'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1223 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::requests:2.28.2'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1224 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: BSD-2-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-2-Clause of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1225 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: BSD-3-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1226 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: ISC |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license ISC of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1227 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1228 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1229 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1230 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1231 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1232 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1233 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1234 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1235 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1236 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1237 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1238 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1239 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1240 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1241 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1242 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1243 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1244 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1245 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1246 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1247 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1248 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1249 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1250 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1251 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1252 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1253 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::requests:2.28.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1254 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::setuptools:67.6.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1255 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::setuptools:67.6.0'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1256 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: BSD-2-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-2-Clause of its dependency 'PyPI::setuptools:67.6.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1257 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: BSD-3-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::setuptools:67.6.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1258 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: GPL-3.0-only |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license GPL-3.0-only of its dependency 'PyPI::setuptools:67.6.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1259 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DECLARED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::setuptools:67.6.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1260 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::setuptools:67.6.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1261 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: MPL-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MPL-2.0 of its dependency 'PyPI::setuptools:67.6.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1262 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::setuptools:67.6.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1263 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::setuptools:67.6.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1264 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::setuptools:67.6.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1265 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::setuptools:67.6.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1266 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::setuptools:67.6.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1267 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::setuptools:67.6.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1268 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::setuptools:67.6.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1269 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::setuptools:67.6.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1270 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::setuptools:67.6.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1271 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::setuptools:67.6.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1272 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::setuptools:67.6.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1273 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::setuptools:67.6.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1274 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::setuptools:67.6.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1275 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: Python-2.0 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::setuptools:67.6.0'. There is insufficient information or knowledge whether the Python-2.0 license is compatible with the EPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the EPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1276 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: Python-2.0 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::setuptools:67.6.0'. There is insufficient information or knowledge whether the Python-2.0 license is compatible with the EPL-2.0 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the EPL-2.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1277 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: Python-2.0 |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::setuptools:67.6.0'. There is insufficient information or knowledge whether the Python-2.0 license is compatible with the MPL-2.0 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the MPL-2.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1278 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: Python-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::setuptools:67.6.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1279 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.0 | DETECTED: Python-2.0 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::setuptools:67.6.0'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1280 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::six:1.16.0 | DECLARED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::six:1.16.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1281 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::six:1.16.0 | DETECTED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::six:1.16.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1282 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::toml:0.10.2 | DECLARED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::toml:0.10.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1283 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::toml:0.10.2 | DETECTED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::toml:0.10.2'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1284 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DECLARED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::tqdm:4.65.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1285 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DETECTED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::tqdm:4.65.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1286 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DECLARED: MPL-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MPL-2.0 of its dependency 'PyPI::tqdm:4.65.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1287 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DETECTED: MPL-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MPL-2.0 of its dependency 'PyPI::tqdm:4.65.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1288 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::tqdm:4.65.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1289 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::tqdm:4.65.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1290 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::tqdm:4.65.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1291 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::tqdm:4.65.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1292 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::tqdm:4.65.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1293 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::tqdm:4.65.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1294 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::tqdm:4.65.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1295 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::tqdm:4.65.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1296 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::tqdm:4.65.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1297 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::tqdm:4.65.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1298 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::tqdm:4.65.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1299 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::tqdm:4.65.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1300 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tqdm:4.65.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::tqdm:4.65.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1301 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::urllib3:1.26.15'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1302 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::urllib3:1.26.15'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1303 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::urllib3:1.26.15'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1304 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license BSD-2-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::urllib3:1.26.15'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1305 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::urllib3:1.26.15'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1306 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::urllib3:1.26.15'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1307 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::urllib3:1.26.15'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1308 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license ISC of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::urllib3:1.26.15'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1309 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::urllib3:1.26.15'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1310 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::urllib3:1.26.15'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1311 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::urllib3:1.26.15'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1312 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::urllib3:1.26.15'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1313 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::urllib3:1.26.15'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1314 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::urllib3:1.26.15'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1315 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license Zlib of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::urllib3:1.26.15'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1316 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DECLARED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::urllib3:1.26.15'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1317 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::urllib3:1.26.15'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1318 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: Python-2.0 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::urllib3:1.26.15'. There is insufficient information or knowledge whether the Python-2.0 license is compatible with the EPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the EPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1319 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: Python-2.0 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::urllib3:1.26.15'. There is insufficient information or knowledge whether the Python-2.0 license is compatible with the EPL-2.0 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the EPL-2.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1320 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: Python-2.0 |
It is unknown whether the outbound license MPL-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::urllib3:1.26.15'. There is insufficient information or knowledge whether the Python-2.0 license is compatible with the MPL-2.0 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the MPL-2.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1321 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: Python-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::urllib3:1.26.15'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1322 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: Python-2.0 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::urllib3:1.26.15'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1323 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::virtualenv:20.21.0 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::virtualenv:20.21.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1324 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::virtualenv:20.21.0 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license OpenSSL of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::virtualenv:20.21.0'. The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. Interpretation: The final statement of the appended SSLeay License "The licence and distribution terms for any publically available version or derivative of this code cannot be changed" normally must be interpreted as a copyleft clause, but there is no general consensus on this interpretation. Therefore, a recommendation on the compatibility of the OpenSSL license can only be given for selected cases. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1325 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::virtualenv:20.21.0 | DETECTED: BSD-3-Clause |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::virtualenv:20.21.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1326 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::virtualenv:20.21.0 | DETECTED: EPL-1.0 |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license EPL-1.0 of its dependency 'PyPI::virtualenv:20.21.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1327 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::virtualenv:20.21.0 | DECLARED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::virtualenv:20.21.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1328 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::virtualenv:20.21.0 | DETECTED: MIT |
It is unknown whether the outbound license NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is compatible with the inbound license MIT of its dependency 'PyPI::virtualenv:20.21.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
1329 | DEPENDENCY_LICENSE_CHECK | PyPI::certifi:2022.12.7 | DETECTED: Python-2.0 |
License Python-2.0 of dependency 'PyPI::certifi:2022.12.7' is unclassified. How to fixClassify Python-2.0 as either approved or restricted. |
1330 | DEPENDENCY_LICENSE_CHECK | PyPI::charset-normalizer:3.1.0 | DETECTED: LicenseRef-scancode-public-domain |
License LicenseRef-scancode-public-domain of dependency 'PyPI::charset-normalizer:3.1.0' is unclassified. How to fixClassify LicenseRef-scancode-public-domain as either approved or restricted. |
1331 | DEPENDENCY_LICENSE_CHECK | PyPI::charset-normalizer:3.1.0 | DETECTED: NOASSERTION |
License NOASSERTION of dependency 'PyPI::charset-normalizer:3.1.0' is unclassified. How to fixClassify NOASSERTION as either approved or restricted. |
1332 | DEPENDENCY_LICENSE_CHECK | PyPI::conan:1.58.0 | DETECTED: GPL-3.0-only |
License GPL-3.0-only of dependency 'PyPI::conan:1.58.0' is unclassified. How to fixClassify GPL-3.0-only as either approved or restricted. |
1333 | DEPENDENCY_LICENSE_CHECK | PyPI::conan:1.58.0 | DETECTED: NOASSERTION |
License NOASSERTION of dependency 'PyPI::conan:1.58.0' is unclassified. How to fixClassify NOASSERTION as either approved or restricted. |
1334 | DEPENDENCY_LICENSE_CHECK | PyPI::conan:1.58.0 | DETECTED: Unlicense |
License Unlicense of dependency 'PyPI::conan:1.58.0' is unclassified. How to fixClassify Unlicense as either approved or restricted. |
1335 | DEPENDENCY_LICENSE_CHECK | PyPI::cpplint:1.6.1 | DETECTED: GPL-2.0-only |
License GPL-2.0-only of dependency 'PyPI::cpplint:1.6.1' is unclassified. How to fixClassify GPL-2.0-only as either approved or restricted. |
1336 | DEPENDENCY_LICENSE_CHECK | PyPI::cpplint:1.6.1 | DECLARED: LicenseRef-scancode-free-unknown |
License LicenseRef-scancode-free-unknown of dependency 'PyPI::cpplint:1.6.1' is unclassified. How to fixClassify LicenseRef-scancode-free-unknown as either approved or restricted. |
1337 | DEPENDENCY_LICENSE_CHECK | PyPI::cpplint:1.6.1 | DETECTED: LicenseRef-scancode-protobuf |
License LicenseRef-scancode-protobuf of dependency 'PyPI::cpplint:1.6.1' is unclassified. How to fixClassify LicenseRef-scancode-protobuf as either approved or restricted. |
1338 | DEPENDENCY_LICENSE_CHECK | PyPI::cpplint:1.6.1 | DETECTED: NOASSERTION |
License NOASSERTION of dependency 'PyPI::cpplint:1.6.1' is unclassified. How to fixClassify NOASSERTION as either approved or restricted. |
1339 | DEPENDENCY_LICENSE_CHECK | PyPI::distlib:0.3.6 | DETECTED: HPND |
License HPND of dependency 'PyPI::distlib:0.3.6' is unclassified. How to fixClassify HPND as either approved or restricted. |
1340 | DEPENDENCY_LICENSE_CHECK | PyPI::distlib:0.3.6 | DETECTED: NOASSERTION |
License NOASSERTION of dependency 'PyPI::distlib:0.3.6' is unclassified. How to fixClassify NOASSERTION as either approved or restricted. |
1341 | DEPENDENCY_LICENSE_CHECK | PyPI::distlib:0.3.6 | DECLARED: PSF-2.0 |
License PSF-2.0 of dependency 'PyPI::distlib:0.3.6' is unclassified. How to fixClassify PSF-2.0 as either approved or restricted. |
1342 | DEPENDENCY_LICENSE_CHECK | PyPI::distlib:0.3.6 | DETECTED: Python-2.0 |
License Python-2.0 of dependency 'PyPI::distlib:0.3.6' is unclassified. How to fixClassify Python-2.0 as either approved or restricted. |
1343 | DEPENDENCY_LICENSE_CHECK | PyPI::filelock:3.10.7 | DETECTED: LicenseRef-scancode-public-domain |
License LicenseRef-scancode-public-domain of dependency 'PyPI::filelock:3.10.7' is unclassified. How to fixClassify LicenseRef-scancode-public-domain as either approved or restricted. |
1344 | DEPENDENCY_LICENSE_CHECK | PyPI::filelock:3.10.7 | DETECTED: NOASSERTION |
License NOASSERTION of dependency 'PyPI::filelock:3.10.7' is unclassified. How to fixClassify NOASSERTION as either approved or restricted. |
1345 | DEPENDENCY_LICENSE_CHECK | PyPI::filelock:3.10.7 | DETECTED: Unlicense |
License Unlicense of dependency 'PyPI::filelock:3.10.7' is unclassified. How to fixClassify Unlicense as either approved or restricted. |
1346 | DEPENDENCY_LICENSE_CHECK | PyPI::gcovr:5.2 | DETECTED: NOASSERTION |
License NOASSERTION of dependency 'PyPI::gcovr:5.2' is unclassified. How to fixClassify NOASSERTION as either approved or restricted. |
1347 | DEPENDENCY_LICENSE_CHECK | PyPI::identify:2.5.22 | DETECTED: AFL-3.0 |
License AFL-3.0 of dependency 'PyPI::identify:2.5.22' is unclassified. How to fixClassify AFL-3.0 as either approved or restricted. |
1348 | DEPENDENCY_LICENSE_CHECK | PyPI::identify:2.5.22 | DETECTED: BSD-3-Clause-Clear |
License BSD-3-Clause-Clear of dependency 'PyPI::identify:2.5.22' is unclassified. How to fixClassify BSD-3-Clause-Clear as either approved or restricted. |
1349 | DEPENDENCY_LICENSE_CHECK | PyPI::identify:2.5.22 | DETECTED: ECL-2.0 |
License ECL-2.0 of dependency 'PyPI::identify:2.5.22' is unclassified. How to fixClassify ECL-2.0 as either approved or restricted. |
1350 | DEPENDENCY_LICENSE_CHECK | PyPI::identify:2.5.22 | DETECTED: EUPL-1.1 |
License EUPL-1.1 of dependency 'PyPI::identify:2.5.22' is unclassified. How to fixClassify EUPL-1.1 as either approved or restricted. |
1351 | DEPENDENCY_LICENSE_CHECK | PyPI::identify:2.5.22 | DETECTED: EUPL-1.2 |
License EUPL-1.2 of dependency 'PyPI::identify:2.5.22' is unclassified. How to fixClassify EUPL-1.2 as either approved or restricted. |
1352 | DEPENDENCY_LICENSE_CHECK | PyPI::identify:2.5.22 | DETECTED: GPL-1.0-or-later |
License GPL-1.0-or-later of dependency 'PyPI::identify:2.5.22' is unclassified. How to fixClassify GPL-1.0-or-later as either approved or restricted. |
1353 | DEPENDENCY_LICENSE_CHECK | PyPI::identify:2.5.22 | DETECTED: GPL-2.0-only |
License GPL-2.0-only of dependency 'PyPI::identify:2.5.22' is unclassified. How to fixClassify GPL-2.0-only as either approved or restricted. |
1354 | DEPENDENCY_LICENSE_CHECK | PyPI::identify:2.5.22 | DETECTED: GPL-3.0-only |
License GPL-3.0-only of dependency 'PyPI::identify:2.5.22' is unclassified. How to fixClassify GPL-3.0-only as either approved or restricted. |
1355 | DEPENDENCY_LICENSE_CHECK | PyPI::identify:2.5.22 | DETECTED: LPPL-1.3c |
License LPPL-1.3c of dependency 'PyPI::identify:2.5.22' is unclassified. How to fixClassify LPPL-1.3c as either approved or restricted. |
1356 | DEPENDENCY_LICENSE_CHECK | PyPI::identify:2.5.22 | DETECTED: MS-PL |
License MS-PL of dependency 'PyPI::identify:2.5.22' is unclassified. How to fixClassify MS-PL as either approved or restricted. |
1357 | DEPENDENCY_LICENSE_CHECK | PyPI::identify:2.5.22 | DETECTED: MS-RL |
License MS-RL of dependency 'PyPI::identify:2.5.22' is unclassified. How to fixClassify MS-RL as either approved or restricted. |
1358 | DEPENDENCY_LICENSE_CHECK | PyPI::identify:2.5.22 | DETECTED: NCSA |
License NCSA of dependency 'PyPI::identify:2.5.22' is unclassified. How to fixClassify NCSA as either approved or restricted. |
1359 | DEPENDENCY_LICENSE_CHECK | PyPI::identify:2.5.22 | DETECTED: NOASSERTION |
License NOASSERTION of dependency 'PyPI::identify:2.5.22' is unclassified. How to fixClassify NOASSERTION as either approved or restricted. |
1360 | DEPENDENCY_LICENSE_CHECK | PyPI::identify:2.5.22 | DETECTED: OSL-3.0 |
License OSL-3.0 of dependency 'PyPI::identify:2.5.22' is unclassified. How to fixClassify OSL-3.0 as either approved or restricted. |
1361 | DEPENDENCY_LICENSE_CHECK | PyPI::identify:2.5.22 | DETECTED: Unlicense |
License Unlicense of dependency 'PyPI::identify:2.5.22' is unclassified. How to fixClassify Unlicense as either approved or restricted. |
1362 | DEPENDENCY_LICENSE_CHECK | PyPI::idna:3.4 | DETECTED: LicenseRef-scancode-unicode |
License LicenseRef-scancode-unicode of dependency 'PyPI::idna:3.4' is unclassified. How to fixClassify LicenseRef-scancode-unicode as either approved or restricted. |
1363 | DEPENDENCY_LICENSE_CHECK | PyPI::jinja2:3.1.2 | DETECTED: LicenseRef-scancode-proprietary-license |
License LicenseRef-scancode-proprietary-license of dependency 'PyPI::jinja2:3.1.2' is unclassified. How to fixClassify LicenseRef-scancode-proprietary-license as either approved or restricted. |
1364 | DEPENDENCY_LICENSE_CHECK | PyPI::lxml:4.9.2 | DETECTED: GPL-1.0-or-later |
License GPL-1.0-or-later of dependency 'PyPI::lxml:4.9.2' is unclassified. How to fixClassify GPL-1.0-or-later as either approved or restricted. |
1365 | DEPENDENCY_LICENSE_CHECK | PyPI::lxml:4.9.2 | DETECTED: GPL-2.0-only |
License GPL-2.0-only of dependency 'PyPI::lxml:4.9.2' is unclassified. How to fixClassify GPL-2.0-only as either approved or restricted. |
1366 | DEPENDENCY_LICENSE_CHECK | PyPI::lxml:4.9.2 | DETECTED: GPL-2.0-or-later |
License GPL-2.0-or-later of dependency 'PyPI::lxml:4.9.2' is unclassified. How to fixClassify GPL-2.0-or-later as either approved or restricted. |
1367 | DEPENDENCY_LICENSE_CHECK | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-proprietary-license |
License LicenseRef-scancode-proprietary-license of dependency 'PyPI::lxml:4.9.2' is unclassified. How to fixClassify LicenseRef-scancode-proprietary-license as either approved or restricted. |
1368 | DEPENDENCY_LICENSE_CHECK | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-public-domain |
License LicenseRef-scancode-public-domain of dependency 'PyPI::lxml:4.9.2' is unclassified. How to fixClassify LicenseRef-scancode-public-domain as either approved or restricted. |
1369 | DEPENDENCY_LICENSE_CHECK | PyPI::lxml:4.9.2 | DETECTED: LicenseRef-scancode-secret-labs-2011 |
License LicenseRef-scancode-secret-labs-2011 of dependency 'PyPI::lxml:4.9.2' is unclassified. How to fixClassify LicenseRef-scancode-secret-labs-2011 as either approved or restricted. |
1370 | DEPENDENCY_LICENSE_CHECK | PyPI::lxml:4.9.2 | DETECTED: NOASSERTION |
License NOASSERTION of dependency 'PyPI::lxml:4.9.2' is unclassified. How to fixClassify NOASSERTION as either approved or restricted. |
1371 | DEPENDENCY_LICENSE_CHECK | PyPI::patch-ng:1.17.4 | DETECTED: GPL-1.0-or-later |
License GPL-1.0-or-later of dependency 'PyPI::patch-ng:1.17.4' is unclassified. How to fixClassify GPL-1.0-or-later as either approved or restricted. |
1372 | DEPENDENCY_LICENSE_CHECK | PyPI::patch-ng:1.17.4 | DETECTED: GPL-3.0-only |
License GPL-3.0-only of dependency 'PyPI::patch-ng:1.17.4' is unclassified. How to fixClassify GPL-3.0-only as either approved or restricted. |
1373 | DEPENDENCY_LICENSE_CHECK | PyPI::pre-commit:2.20.0 | DETECTED: GPL-3.0-only |
License GPL-3.0-only of dependency 'PyPI::pre-commit:2.20.0' is unclassified. How to fixClassify GPL-3.0-only as either approved or restricted. |
1374 | DEPENDENCY_LICENSE_CHECK | PyPI::pygments:2.14.0 | DETECTED: AFL-3.0 |
License AFL-3.0 of dependency 'PyPI::pygments:2.14.0' is unclassified. How to fixClassify AFL-3.0 as either approved or restricted. |
1375 | DEPENDENCY_LICENSE_CHECK | PyPI::pygments:2.14.0 | DETECTED: Apache-2.0 WITH LLVM-exception |
License Apache-2.0 WITH LLVM-exception of dependency 'PyPI::pygments:2.14.0' is unclassified. How to fixClassify Apache-2.0 WITH LLVM-exception as either approved or restricted. |
1376 | DEPENDENCY_LICENSE_CHECK | PyPI::pygments:2.14.0 | DETECTED: GPL-1.0-or-later |
License GPL-1.0-or-later of dependency 'PyPI::pygments:2.14.0' is unclassified. How to fixClassify GPL-1.0-or-later as either approved or restricted. |
1377 | DEPENDENCY_LICENSE_CHECK | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-only |
License GPL-2.0-only of dependency 'PyPI::pygments:2.14.0' is unclassified. How to fixClassify GPL-2.0-only as either approved or restricted. |
1378 | DEPENDENCY_LICENSE_CHECK | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later |
License GPL-2.0-or-later of dependency 'PyPI::pygments:2.14.0' is unclassified. How to fixClassify GPL-2.0-or-later as either approved or restricted. |
1379 | DEPENDENCY_LICENSE_CHECK | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0 |
License GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0 of dependency 'PyPI::pygments:2.14.0' is unclassified. How to fixClassify GPL-2.0-or-later WITH LicenseRef-scancode-autoconf-simple-exception-2.0 as either approved or restricted. |
1380 | DEPENDENCY_LICENSE_CHECK | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0 |
License GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0 of dependency 'PyPI::pygments:2.14.0' is unclassified. How to fixClassify GPL-2.0-or-later WITH LicenseRef-scancode-bison-exception-2.0 as either approved or restricted. |
1381 | DEPENDENCY_LICENSE_CHECK | PyPI::pygments:2.14.0 | DETECTED: GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0 |
License GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0 of dependency 'PyPI::pygments:2.14.0' is unclassified. How to fixClassify GPL-2.0-or-later WITH LicenseRef-scancode-guile-exception-2.0 as either approved or restricted. |
1382 | DEPENDENCY_LICENSE_CHECK | PyPI::pygments:2.14.0 | DETECTED: GPL-3.0-only |
License GPL-3.0-only of dependency 'PyPI::pygments:2.14.0' is unclassified. How to fixClassify GPL-3.0-only as either approved or restricted. |
1383 | DEPENDENCY_LICENSE_CHECK | PyPI::pygments:2.14.0 | DETECTED: GPL-3.0-or-later |
License GPL-3.0-or-later of dependency 'PyPI::pygments:2.14.0' is unclassified. How to fixClassify GPL-3.0-or-later as either approved or restricted. |
1384 | DEPENDENCY_LICENSE_CHECK | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception |
License LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception of dependency 'PyPI::pygments:2.14.0' is unclassified. How to fixClassify LGPL-2.0-or-later WITH OCaml-LGPL-linking-exception as either approved or restricted. |
1385 | DEPENDENCY_LICENSE_CHECK | PyPI::pygments:2.14.0 | DETECTED: LGPL-2.1-only WITH Qt-LGPL-exception-1.1 |
License LGPL-2.1-only WITH Qt-LGPL-exception-1.1 of dependency 'PyPI::pygments:2.14.0' is unclassified. How to fixClassify LGPL-2.1-only WITH Qt-LGPL-exception-1.1 as either approved or restricted. |
1386 | DEPENDENCY_LICENSE_CHECK | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-commercial-license |
License LicenseRef-scancode-commercial-license of dependency 'PyPI::pygments:2.14.0' is unclassified. How to fixClassify LicenseRef-scancode-commercial-license as either approved or restricted. |
1387 | DEPENDENCY_LICENSE_CHECK | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-iso-8879 |
License LicenseRef-scancode-iso-8879 of dependency 'PyPI::pygments:2.14.0' is unclassified. How to fixClassify LicenseRef-scancode-iso-8879 as either approved or restricted. |
1388 | DEPENDENCY_LICENSE_CHECK | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-proprietary-license |
License LicenseRef-scancode-proprietary-license of dependency 'PyPI::pygments:2.14.0' is unclassified. How to fixClassify LicenseRef-scancode-proprietary-license as either approved or restricted. |
1389 | DEPENDENCY_LICENSE_CHECK | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-public-domain |
License LicenseRef-scancode-public-domain of dependency 'PyPI::pygments:2.14.0' is unclassified. How to fixClassify LicenseRef-scancode-public-domain as either approved or restricted. |
1390 | DEPENDENCY_LICENSE_CHECK | PyPI::pygments:2.14.0 | DETECTED: LicenseRef-scancode-public-domain-disclaimer |
License LicenseRef-scancode-public-domain-disclaimer of dependency 'PyPI::pygments:2.14.0' is unclassified. How to fixClassify LicenseRef-scancode-public-domain-disclaimer as either approved or restricted. |
1391 | DEPENDENCY_LICENSE_CHECK | PyPI::pygments:2.14.0 | DETECTED: MIT-Modern-Variant |
License MIT-Modern-Variant of dependency 'PyPI::pygments:2.14.0' is unclassified. How to fixClassify MIT-Modern-Variant as either approved or restricted. |
1392 | DEPENDENCY_LICENSE_CHECK | PyPI::pygments:2.14.0 | DETECTED: NOASSERTION |
License NOASSERTION of dependency 'PyPI::pygments:2.14.0' is unclassified. How to fixClassify NOASSERTION as either approved or restricted. |
1393 | DEPENDENCY_LICENSE_CHECK | PyPI::python-dateutil:2.8.2 | DETECTED: NOASSERTION |
License NOASSERTION of dependency 'PyPI::python-dateutil:2.8.2' is unclassified. How to fixClassify NOASSERTION as either approved or restricted. |
1394 | DEPENDENCY_LICENSE_CHECK | PyPI::python-dateutil:2.8.2 | DETECTED: Python-2.0 |
License Python-2.0 of dependency 'PyPI::python-dateutil:2.8.2' is unclassified. How to fixClassify Python-2.0 as either approved or restricted. |
1395 | DEPENDENCY_LICENSE_CHECK | PyPI::requests:2.28.2 | DETECTED: NOASSERTION |
License NOASSERTION of dependency 'PyPI::requests:2.28.2' is unclassified. How to fixClassify NOASSERTION as either approved or restricted. |
1396 | DEPENDENCY_LICENSE_CHECK | PyPI::setuptools:67.6.0 | DETECTED: GPL-3.0-only |
License GPL-3.0-only of dependency 'PyPI::setuptools:67.6.0' is unclassified. How to fixClassify GPL-3.0-only as either approved or restricted. |
1397 | DEPENDENCY_LICENSE_CHECK | PyPI::setuptools:67.6.0 | DETECTED: NOASSERTION |
License NOASSERTION of dependency 'PyPI::setuptools:67.6.0' is unclassified. How to fixClassify NOASSERTION as either approved or restricted. |
1398 | DEPENDENCY_LICENSE_CHECK | PyPI::setuptools:67.6.0 | DETECTED: Python-2.0 |
License Python-2.0 of dependency 'PyPI::setuptools:67.6.0' is unclassified. How to fixClassify Python-2.0 as either approved or restricted. |
1399 | DEPENDENCY_LICENSE_CHECK | PyPI::tqdm:4.65.0 | DETECTED: NOASSERTION |
License NOASSERTION of dependency 'PyPI::tqdm:4.65.0' is unclassified. How to fixClassify NOASSERTION as either approved or restricted. |
1400 | DEPENDENCY_LICENSE_CHECK | PyPI::urllib3:1.26.15 | DETECTED: LicenseRef-scancode-public-domain |
License LicenseRef-scancode-public-domain of dependency 'PyPI::urllib3:1.26.15' is unclassified. How to fixClassify LicenseRef-scancode-public-domain as either approved or restricted. |
1401 | DEPENDENCY_LICENSE_CHECK | PyPI::urllib3:1.26.15 | DETECTED: Python-2.0 |
License Python-2.0 of dependency 'PyPI::urllib3:1.26.15' is unclassified. How to fixClassify Python-2.0 as either approved or restricted. |
1402 | PROJECT_LICENSE_CHECK | Conan::conanfile.txt: | DETECTED: NOASSERTION |
License NOASSERTION of project 'Conan::conanfile.txt:' is unclassified. How to fixClassify NOASSERTION as either approved or restricted. |
1403 | PROJECT_LICENSE_CHECK | Conan::conanfile.txt: | DETECTED: Python-2.0 |
License Python-2.0 of project 'Conan::conanfile.txt:' is unclassified. How to fixClassify Python-2.0 as either approved or restricted. |
1404 | PROJECT_LICENSE_CHECK | Conan::conanfile.txt: | DETECTED: Unlicense |
License Unlicense of project 'Conan::conanfile.txt:' is unclassified. How to fixClassify Unlicense as either approved or restricted. |
1405 | PROJECT_LICENSE_CHECK | PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac | DETECTED: NOASSERTION |
License NOASSERTION of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is unclassified. How to fixClassify NOASSERTION as either approved or restricted. |
1406 | PROJECT_LICENSE_CHECK | PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac | DETECTED: Python-2.0 |
License Python-2.0 of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is unclassified. How to fixClassify Python-2.0 as either approved or restricted. |
1407 | PROJECT_LICENSE_CHECK | PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac | DETECTED: Unlicense |
License Unlicense of project 'PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac' is unclassified. How to fixClassify Unlicense as either approved or restricted. |
Type | Git |
URL | https://github.com/eclipse-velocitas/vehicle-app-cpp-template.git |
Path | |
Revision | 51c092d4c0337a7651883a9e63626a8cfe42aaac |
# | Package | Scopes | Licenses | Analyzer Issues | Scanner Issues |
---|---|---|---|---|---|
1 | Conan::conanfile.txt: | Detected Licenses (from VCS):
|
|
|
Type | Git |
URL | https://github.com/eclipse-velocitas/vehicle-app-cpp-template.git |
Path | |
Revision | 51c092d4c0337a7651883a9e63626a8cfe42aaac |
# | Package | Scopes | Licenses | Analyzer Issues | Scanner Issues |
---|---|---|---|---|---|
1 | PIP::requirements.txt:51c092d4c0337a7651883a9e63626a8cfe42aaac | Detected Licenses (from VCS):
|
|
|
|
2 | PyPI::bottle:0.12.25 |
|
Declared Licenses: |
|
|
3 | PyPI::certifi:2022.12.7 |
|
Declared Licenses:
|
|
|
4 | PyPI::cfgv:3.3.1 |
|
Declared Licenses: |
|
|
5 | PyPI::charset-normalizer:3.1.0 |
|
Declared Licenses:
|
|
|
6 | PyPI::colorama:0.4.6 |
|
Detected Licenses (from artifact): |
|
|
7 | PyPI::conan:1.58.0 |
|
Declared Licenses:
|
|
|
8 | PyPI::cpplint:1.6.1 |
|
Declared Licenses:
|
|
|
9 | PyPI::distlib:0.3.6 |
|
Declared Licenses:
|
|
|
10 | PyPI::distro:1.7.0 |
|
Declared Licenses:
|
|
|
11 | PyPI::fasteners:0.18 |
|
Declared Licenses:
|
|
|
12 | PyPI::filelock:3.10.7 |
|
Detected Licenses (from VCS):Effective License:
|
|
|
13 | PyPI::gcovr:5.2 |
|
Declared Licenses:
|
|
|
14 | PyPI::identify:2.5.22 |
|
Declared Licenses:
|
|
|
15 | PyPI::idna:3.4 |
|
Detected Licenses (from VCS):
|
|
|
16 | PyPI::jinja2:3.1.2 |
|
Declared Licenses:
|
|
|
17 | PyPI::lxml:4.9.2 |
|
Declared Licenses:
|
|
|
18 | PyPI::markupsafe:2.1.2 |
|
Declared Licenses:
|
|
|
19 | PyPI::node-semver:0.6.1 |
|
Declared Licenses: |
|
|
20 | PyPI::nodeenv:1.7.0 |
|
Declared Licenses:
|
|
|
21 | PyPI::patch-ng:1.17.4 |
|
Declared Licenses:
|
|
|
22 | PyPI::platformdirs:3.2.0 |
|
Declared Licenses: |
|
|
23 | PyPI::pluginbase:1.0.1 |
|
Detected Licenses (from VCS):
|
|
|
24 | PyPI::pre-commit:2.20.0 |
|
Declared Licenses:
|
|
|
25 | PyPI::pygments:2.14.0 |
|
Declared Licenses:
|
|
|
26 | PyPI::pyjwt:2.6.0 |
|
Declared Licenses: |
|
|
27 | PyPI::python-dateutil:2.8.2 |
|
Declared Licenses:
|
|
|
28 | PyPI::pyyaml:6.0 |
|
Declared Licenses: |
|
|
29 | PyPI::requests:2.28.2 |
|
Declared Licenses:
|
|
|
30 | PyPI::setuptools:67.6.0 |
|
Declared Licenses:
|
|
|
31 | PyPI::six:1.16.0 |
|
Declared Licenses: |
|
|
32 | PyPI::toml:0.10.2 |
|
Declared Licenses: |
|
|
33 | PyPI::tqdm:4.65.0 |
|
Declared Licenses:
|
|
|
34 | PyPI::urllib3:1.26.15 |
|
Declared Licenses:
|
|
|
35 | PyPI::virtualenv:20.21.0 |
|
Declared Licenses:
|
|
|
---
excludes:
paths:
- pattern: "**/META-INF/DEPENDENCIES"
reason: "BUILD_TOOL_OF"
comment: "Licenses contained in this directory reflect content analysed elsewhere."
- pattern: "**/META-INF/NOTICE*"
reason: "BUILD_TOOL_OF"
comment: "Licenses contained in this directory reflect content analysed elsewhere."
- pattern: "**/*.svg"
reason: "BUILD_TOOL_OF"
comment: "SVG files do not contain any license information."
- pattern: "package-lock.json"
reason: "BUILD_TOOL_OF"
comment: "Does not contain any license information."