# | Rule | Package | License | Message |
---|---|---|---|---|
1 | DEPENDENCY_LICENSE_CHECK | PyPI::pytest:7.2.2 | DETECTED: JSON |
License JSON of dependency 'PyPI::pytest:7.2.2' is classified as restricted. How to fixRemove dependency 'PyPI::pytest:7.2.2' from project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06'. |
2 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::argcomplete:3.0.5 | DECLARED: Apache-2.0 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::argcomplete:3.0.5'. Incompatibility of the Apache-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. How to fixRemove the dependency on 'PyPI::argcomplete:3.0.5' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
3 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::argcomplete:3.0.5 | DETECTED: Apache-2.0 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::argcomplete:3.0.5'. Incompatibility of the Apache-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. How to fixRemove the dependency on 'PyPI::argcomplete:3.0.5' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
4 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::argcomplete:3.0.5 | DECLARED: Apache-2.0 |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::argcomplete:3.0.5'. Incompatibility of the Apache-2.0 license with the MPL-1.1 license is explicitly stated in the MPL-1.1 license checklist. How to fixRemove the dependency on 'PyPI::argcomplete:3.0.5' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
5 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::argcomplete:3.0.5 | DETECTED: Apache-2.0 |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::argcomplete:3.0.5'. Incompatibility of the Apache-2.0 license with the MPL-1.1 license is explicitly stated in the MPL-1.1 license checklist. How to fixRemove the dependency on 'PyPI::argcomplete:3.0.5' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
6 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.1-only |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::astroid:2.15.2'. 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::astroid:2.15.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
7 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.1-only |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::astroid:2.15.2'. 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::astroid:2.15.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
8 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.1-only |
The outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::astroid:2.15.2'. Software under a copyleft license such as the LGPL-2.1-only license normally cannot be redistributed under another copyleft license such as the CPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::astroid:2.15.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
9 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.1-only |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::astroid:2.15.2'. 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::astroid:2.15.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
10 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.1-only |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::astroid:2.15.2'. 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::astroid:2.15.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
11 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.1-only |
The outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::astroid:2.15.2'. 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::astroid:2.15.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
12 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.1-only |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::astroid:2.15.2'. 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-1.1 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::astroid:2.15.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
13 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DECLARED: LGPL-2.1-or-later |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::astroid:2.15.2'. 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::astroid:2.15.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
14 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.1-or-later |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::astroid:2.15.2'. 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::astroid:2.15.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
15 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DECLARED: LGPL-2.1-or-later |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::astroid:2.15.2'. 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::astroid:2.15.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
16 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.1-or-later |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::astroid:2.15.2'. 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::astroid:2.15.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
17 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DECLARED: LGPL-2.1-or-later |
The outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::astroid:2.15.2'. 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 CPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::astroid:2.15.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
18 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.1-or-later |
The outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::astroid:2.15.2'. 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 CPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::astroid:2.15.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
19 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DECLARED: LGPL-2.1-or-later |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::astroid:2.15.2'. 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::astroid:2.15.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
20 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.1-or-later |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::astroid:2.15.2'. 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::astroid:2.15.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
21 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DECLARED: LGPL-2.1-or-later |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::astroid:2.15.2'. 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::astroid:2.15.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
22 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.1-or-later |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::astroid:2.15.2'. 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::astroid:2.15.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
23 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DECLARED: LGPL-2.1-or-later |
The outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::astroid:2.15.2'. 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::astroid:2.15.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
24 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.1-or-later |
The outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::astroid:2.15.2'. 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::astroid:2.15.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
25 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DECLARED: LGPL-2.1-or-later |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::astroid:2.15.2'. 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-1.1 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::astroid:2.15.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
26 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.1-or-later |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::astroid:2.15.2'. 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-1.1 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::astroid:2.15.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
27 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DECLARED: MPL-2.0 |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
28 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: MPL-2.0 |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
29 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DECLARED: MPL-2.0 |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
30 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: MPL-2.0 |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
31 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DECLARED: MPL-2.0 |
The outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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 CPL-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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
32 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: MPL-2.0 |
The outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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 CPL-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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
33 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DECLARED: MPL-2.0 |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
34 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: MPL-2.0 |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
35 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DECLARED: MPL-2.0 |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
36 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: MPL-2.0 |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
37 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DECLARED: MPL-2.0 |
The outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
38 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: MPL-2.0 |
The outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
39 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DECLARED: MPL-2.0 |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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 MPL-1.1 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
40 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: MPL-2.0 |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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 MPL-1.1 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
41 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: Python-2.0 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Python-2.0 of its dependency 'PyPI::certifi:2022.12.7'. Incompatibility of the Python-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. Interpretation: The requirement of the Python license to provide a brief summary of the changes may definitely be seen as a further restriction the final license prohibits to impose, since it requires to describe the changes rather than only to mention the fact that changes were made and such brief summary must be included in source code and binary delivery. However, another interpretation may argue that the final license requires at least disclosure, though not always inclusion, of the complete corresponding source code which enables a sufficiently well trained engineer to extract the differences, understand the changes and derive a summary which then would be, at least partly, in line with the Python license requirement. How to fixRemove the dependency on 'PyPI::certifi:2022.12.7' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
42 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
43 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
44 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LGPL-2.1-only |
The outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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 CPL-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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
45 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
46 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
47 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LGPL-2.1-only |
The outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
48 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LGPL-2.1-only |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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-1.1 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
49 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
50 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
51 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: MPL-1.1 |
The outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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 CPL-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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
52 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
53 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
54 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: MPL-1.1 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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 GPL-1.0-or-later 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
55 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: MPL-1.1 |
The outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
56 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DECLARED: Apache-2.0 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::coverage:7.2.3'. Incompatibility of the Apache-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. How to fixRemove the dependency on 'PyPI::coverage:7.2.3' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
57 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: Apache-2.0 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::coverage:7.2.3'. Incompatibility of the Apache-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. How to fixRemove the dependency on 'PyPI::coverage:7.2.3' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
58 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DECLARED: Apache-2.0 |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::coverage:7.2.3'. Incompatibility of the Apache-2.0 license with the MPL-1.1 license is explicitly stated in the MPL-1.1 license checklist. How to fixRemove the dependency on 'PyPI::coverage:7.2.3' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
59 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: Apache-2.0 |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::coverage:7.2.3'. Incompatibility of the Apache-2.0 license with the MPL-1.1 license is explicitly stated in the MPL-1.1 license checklist. How to fixRemove the dependency on 'PyPI::coverage:7.2.3' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
60 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: GPL-2.0-only |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::coverage:7.2.3'. 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::coverage:7.2.3' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
61 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: GPL-2.0-only |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::coverage:7.2.3'. 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::coverage:7.2.3' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
62 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: GPL-2.0-only |
The outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::coverage:7.2.3'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under another copyleft license such as the CPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::coverage:7.2.3' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
63 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: GPL-2.0-only |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::coverage:7.2.3'. 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::coverage:7.2.3' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
64 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: GPL-2.0-only |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::coverage:7.2.3'. 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::coverage:7.2.3' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
65 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: GPL-2.0-only |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::coverage:7.2.3'. Software under a copyleft license such as the GPL-2.0-only license normally cannot be redistributed under another copyleft license such as the GPL-1.0-or-later license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::coverage:7.2.3' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
66 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: GPL-2.0-only |
The outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::coverage:7.2.3'. 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::coverage:7.2.3' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
67 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: GPL-2.0-only |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::coverage:7.2.3'. 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-1.1 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::coverage:7.2.3' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
68 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::dill:0.3.6 | DETECTED: Apache-2.0 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::dill:0.3.6'. Incompatibility of the Apache-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. How to fixRemove the dependency on 'PyPI::dill:0.3.6' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
69 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::dill:0.3.6 | DETECTED: Apache-2.0 |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::dill:0.3.6'. Incompatibility of the Apache-2.0 license with the MPL-1.1 license is explicitly stated in the MPL-1.1 license checklist. How to fixRemove the dependency on 'PyPI::dill:0.3.6' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
70 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::exceptiongroup:1.1.1 | DETECTED: Python-2.0 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Python-2.0 of its dependency 'PyPI::exceptiongroup:1.1.1'. Incompatibility of the Python-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. Interpretation: The requirement of the Python license to provide a brief summary of the changes may definitely be seen as a further restriction the final license prohibits to impose, since it requires to describe the changes rather than only to mention the fact that changes were made and such brief summary must be included in source code and binary delivery. However, another interpretation may argue that the final license requires at least disclosure, though not always inclusion, of the complete corresponding source code which enables a sufficiently well trained engineer to extract the differences, understand the changes and derive a summary which then would be, at least partly, in line with the Python license requirement. How to fixRemove the dependency on 'PyPI::exceptiongroup:1.1.1' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
71 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::isort:5.12.0 | DETECTED: Apache-2.0 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::isort:5.12.0'. Incompatibility of the Apache-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. How to fixRemove the dependency on 'PyPI::isort:5.12.0' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
72 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::isort:5.12.0 | DETECTED: Apache-2.0 |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::isort:5.12.0'. Incompatibility of the Apache-2.0 license with the MPL-1.1 license is explicitly stated in the MPL-1.1 license checklist. How to fixRemove the dependency on 'PyPI::isort:5.12.0' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
73 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: Apache-2.0 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::numpy:1.24.2'. Incompatibility of the Apache-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. How to fixRemove the dependency on 'PyPI::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
74 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: Apache-2.0 |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::numpy:1.24.2'. Incompatibility of the Apache-2.0 license with the MPL-1.1 license is explicitly stated in the MPL-1.1 license checklist. How to fixRemove the dependency on 'PyPI::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
75 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-only |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::numpy:1.24.2'. 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::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
76 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-only |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::numpy:1.24.2'. 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::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
77 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-only |
The outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::numpy:1.24.2'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under another copyleft license such as the CPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
78 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-only |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::numpy:1.24.2'. 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::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
79 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-only |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::numpy:1.24.2'. 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::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
80 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-only |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::numpy:1.24.2'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under another copyleft license such as the GPL-1.0-or-later license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
81 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-only |
The outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::numpy:1.24.2'. 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::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
82 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-only |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::numpy:1.24.2'. 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-1.1 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
83 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-only WITH GCC-exception-3.1 |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-only (simplified from 'GPL-3.0-only WITH GCC-exception-3.1') of its dependency 'PyPI::numpy:1.24.2'. 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::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
84 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-only WITH GCC-exception-3.1 |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-only (simplified from 'GPL-3.0-only WITH GCC-exception-3.1') of its dependency 'PyPI::numpy:1.24.2'. 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::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
85 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-only WITH GCC-exception-3.1 |
The outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-only (simplified from 'GPL-3.0-only WITH GCC-exception-3.1') of its dependency 'PyPI::numpy:1.24.2'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under another copyleft license such as the CPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
86 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-only WITH GCC-exception-3.1 |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-only (simplified from 'GPL-3.0-only WITH GCC-exception-3.1') of its dependency 'PyPI::numpy:1.24.2'. 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::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
87 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-only WITH GCC-exception-3.1 |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-only (simplified from 'GPL-3.0-only WITH GCC-exception-3.1') of its dependency 'PyPI::numpy:1.24.2'. 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::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
88 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-only WITH GCC-exception-3.1 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-only (simplified from 'GPL-3.0-only WITH GCC-exception-3.1') of its dependency 'PyPI::numpy:1.24.2'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under another copyleft license such as the GPL-1.0-or-later license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
89 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-only WITH GCC-exception-3.1 |
The outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-only (simplified from 'GPL-3.0-only WITH GCC-exception-3.1') of its dependency 'PyPI::numpy:1.24.2'. 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::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
90 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-only WITH GCC-exception-3.1 |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-only (simplified from 'GPL-3.0-only WITH GCC-exception-3.1') of its dependency 'PyPI::numpy:1.24.2'. 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-1.1 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
91 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-or-later |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-or-later of its dependency 'PyPI::numpy:1.24.2'. 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::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
92 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-or-later |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-or-later of its dependency 'PyPI::numpy:1.24.2'. 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::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
93 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-or-later |
The outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-or-later of its dependency 'PyPI::numpy:1.24.2'. 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 CPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
94 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-or-later |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-or-later of its dependency 'PyPI::numpy:1.24.2'. 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::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
95 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-or-later |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-or-later of its dependency 'PyPI::numpy:1.24.2'. 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::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
96 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-or-later |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-or-later of its dependency 'PyPI::numpy:1.24.2'. 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 GPL-1.0-or-later license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
97 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-or-later |
The outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-or-later of its dependency 'PyPI::numpy:1.24.2'. 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::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
98 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-or-later |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-or-later of its dependency 'PyPI::numpy:1.24.2'. 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-1.1 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
99 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-or-later WITH GCC-exception-3.1 |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-or-later (simplified from 'GPL-3.0-or-later WITH GCC-exception-3.1') of its dependency 'PyPI::numpy:1.24.2'. 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::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
100 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-or-later WITH GCC-exception-3.1 |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-or-later (simplified from 'GPL-3.0-or-later WITH GCC-exception-3.1') of its dependency 'PyPI::numpy:1.24.2'. 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::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
101 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-or-later WITH GCC-exception-3.1 |
The outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-or-later (simplified from 'GPL-3.0-or-later WITH GCC-exception-3.1') of its dependency 'PyPI::numpy:1.24.2'. 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 CPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
102 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-or-later WITH GCC-exception-3.1 |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-or-later (simplified from 'GPL-3.0-or-later WITH GCC-exception-3.1') of its dependency 'PyPI::numpy:1.24.2'. 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::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
103 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-or-later WITH GCC-exception-3.1 |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-or-later (simplified from 'GPL-3.0-or-later WITH GCC-exception-3.1') of its dependency 'PyPI::numpy:1.24.2'. 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::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
104 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-or-later WITH GCC-exception-3.1 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-or-later (simplified from 'GPL-3.0-or-later WITH GCC-exception-3.1') of its dependency 'PyPI::numpy:1.24.2'. 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 GPL-1.0-or-later license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
105 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-or-later WITH GCC-exception-3.1 |
The outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-or-later (simplified from 'GPL-3.0-or-later WITH GCC-exception-3.1') of its dependency 'PyPI::numpy:1.24.2'. 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::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
106 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-or-later WITH GCC-exception-3.1 |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-or-later (simplified from 'GPL-3.0-or-later WITH GCC-exception-3.1') of its dependency 'PyPI::numpy:1.24.2'. 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-1.1 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::numpy:1.24.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
107 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::packaging:23.0 | DECLARED: Apache-2.0 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::packaging:23.0'. Incompatibility of the Apache-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. How to fixRemove the dependency on 'PyPI::packaging:23.0' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
108 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::packaging:23.0 | DETECTED: Apache-2.0 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::packaging:23.0'. Incompatibility of the Apache-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. How to fixRemove the dependency on 'PyPI::packaging:23.0' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
109 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::packaging:23.0 | DECLARED: Apache-2.0 |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::packaging:23.0'. Incompatibility of the Apache-2.0 license with the MPL-1.1 license is explicitly stated in the MPL-1.1 license checklist. How to fixRemove the dependency on 'PyPI::packaging:23.0' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
110 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::packaging:23.0 | DETECTED: Apache-2.0 |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::packaging:23.0'. Incompatibility of the Apache-2.0 license with the MPL-1.1 license is explicitly stated in the MPL-1.1 license checklist. How to fixRemove the dependency on 'PyPI::packaging:23.0' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
111 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pandas:2.0.0 | DETECTED: Apache-2.0 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::pandas:2.0.0'. Incompatibility of the Apache-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. How to fixRemove the dependency on 'PyPI::pandas:2.0.0' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
112 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pandas:2.0.0 | DETECTED: Apache-2.0 |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::pandas:2.0.0'. Incompatibility of the Apache-2.0 license with the MPL-1.1 license is explicitly stated in the MPL-1.1 license checklist. How to fixRemove the dependency on 'PyPI::pandas:2.0.0' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
113 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pandas:2.0.0 | DETECTED: MPL-1.1 |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::pandas:2.0.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::pandas:2.0.0' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
114 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pandas:2.0.0 | DETECTED: MPL-1.1 |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::pandas:2.0.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::pandas:2.0.0' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
115 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pandas:2.0.0 | DETECTED: MPL-1.1 |
The outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::pandas:2.0.0'. Software under a copyleft license such as the MPL-1.1 license normally cannot be redistributed under another copyleft license such as the CPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pandas:2.0.0' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
116 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pandas:2.0.0 | DETECTED: MPL-1.1 |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::pandas:2.0.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::pandas:2.0.0' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
117 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pandas:2.0.0 | DETECTED: MPL-1.1 |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::pandas:2.0.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::pandas:2.0.0' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
118 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pandas:2.0.0 | DETECTED: MPL-1.1 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::pandas:2.0.0'. Software under a copyleft license such as the MPL-1.1 license normally cannot be redistributed under another copyleft license such as the GPL-1.0-or-later license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pandas:2.0.0' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
119 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pandas:2.0.0 | DETECTED: MPL-1.1 |
The outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license MPL-1.1 of its dependency 'PyPI::pandas:2.0.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::pandas:2.0.0' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
120 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pandas:2.0.0 | DETECTED: MPL-2.0 |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::pandas:2.0.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::pandas:2.0.0' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
121 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pandas:2.0.0 | DETECTED: MPL-2.0 |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::pandas:2.0.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::pandas:2.0.0' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
122 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pandas:2.0.0 | DETECTED: MPL-2.0 |
The outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::pandas:2.0.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under another copyleft license such as the CPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pandas:2.0.0' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
123 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pandas:2.0.0 | DETECTED: MPL-2.0 |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::pandas:2.0.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::pandas:2.0.0' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
124 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pandas:2.0.0 | DETECTED: MPL-2.0 |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::pandas:2.0.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::pandas:2.0.0' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
125 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pandas:2.0.0 | DETECTED: MPL-2.0 |
The outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::pandas:2.0.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::pandas:2.0.0' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
126 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pandas:2.0.0 | DETECTED: MPL-2.0 |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::pandas:2.0.0'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under another copyleft license such as the MPL-1.1 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pandas:2.0.0' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
127 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pandas:2.0.0 | DETECTED: Python-2.0 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Python-2.0 of its dependency 'PyPI::pandas:2.0.0'. Incompatibility of the Python-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. Interpretation: The requirement of the Python license to provide a brief summary of the changes may definitely be seen as a further restriction the final license prohibits to impose, since it requires to describe the changes rather than only to mention the fact that changes were made and such brief summary must be included in source code and binary delivery. However, another interpretation may argue that the final license requires at least disclosure, though not always inclusion, of the complete corresponding source code which enables a sufficiently well trained engineer to extract the differences, understand the changes and derive a summary which then would be, at least partly, in line with the Python license requirement. How to fixRemove the dependency on 'PyPI::pandas:2.0.0' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
128 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: GPL-1.0-or-later |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::pylint:2.17.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::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
129 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: GPL-1.0-or-later |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::pylint:2.17.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::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
130 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: GPL-1.0-or-later |
The outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::pylint:2.17.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 CPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
131 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: GPL-1.0-or-later |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::pylint:2.17.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::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
132 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: GPL-1.0-or-later |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::pylint:2.17.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::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
133 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: GPL-1.0-or-later |
The outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::pylint:2.17.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::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
134 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: GPL-1.0-or-later |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::pylint:2.17.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-1.1 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
135 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DECLARED: GPL-2.0-only |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pylint:2.17.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::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
136 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: GPL-2.0-only |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pylint:2.17.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::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
137 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DECLARED: GPL-2.0-only |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pylint:2.17.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::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
138 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: GPL-2.0-only |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pylint:2.17.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::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
139 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DECLARED: GPL-2.0-only |
The outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pylint:2.17.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 CPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
140 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: GPL-2.0-only |
The outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pylint:2.17.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 CPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
141 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DECLARED: GPL-2.0-only |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pylint:2.17.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::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
142 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: GPL-2.0-only |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pylint:2.17.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::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
143 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DECLARED: GPL-2.0-only |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pylint:2.17.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::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
144 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: GPL-2.0-only |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pylint:2.17.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::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
145 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DECLARED: GPL-2.0-only |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pylint:2.17.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 GPL-1.0-or-later license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
146 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: GPL-2.0-only |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pylint:2.17.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 GPL-1.0-or-later license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
147 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DECLARED: GPL-2.0-only |
The outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pylint:2.17.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::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
148 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: GPL-2.0-only |
The outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pylint:2.17.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::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
149 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DECLARED: GPL-2.0-only |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pylint:2.17.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-1.1 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
150 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: GPL-2.0-only |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pylint:2.17.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-1.1 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
151 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DECLARED: GPL-2.0-or-later |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pylint:2.17.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::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
152 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: GPL-2.0-or-later |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pylint:2.17.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::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
153 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DECLARED: GPL-2.0-or-later |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pylint:2.17.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::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
154 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: GPL-2.0-or-later |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pylint:2.17.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::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
155 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DECLARED: GPL-2.0-or-later |
The outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pylint:2.17.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 CPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
156 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: GPL-2.0-or-later |
The outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pylint:2.17.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 CPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
157 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DECLARED: GPL-2.0-or-later |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pylint:2.17.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::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
158 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: GPL-2.0-or-later |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pylint:2.17.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::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
159 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DECLARED: GPL-2.0-or-later |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pylint:2.17.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::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
160 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: GPL-2.0-or-later |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pylint:2.17.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::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
161 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DECLARED: GPL-2.0-or-later |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pylint:2.17.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 GPL-1.0-or-later license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
162 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: GPL-2.0-or-later |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pylint:2.17.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 GPL-1.0-or-later license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
163 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DECLARED: GPL-2.0-or-later |
The outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pylint:2.17.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::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
164 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: GPL-2.0-or-later |
The outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pylint:2.17.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::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
165 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DECLARED: GPL-2.0-or-later |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pylint:2.17.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-1.1 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
166 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: GPL-2.0-or-later |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pylint:2.17.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-1.1 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::pylint:2.17.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
167 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DECLARED: Apache-2.0 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::python-dateutil:2.8.2'. Incompatibility of the Apache-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. How to fixRemove the dependency on 'PyPI::python-dateutil:2.8.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
168 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: Apache-2.0 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::python-dateutil:2.8.2'. Incompatibility of the Apache-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. How to fixRemove the dependency on 'PyPI::python-dateutil:2.8.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
169 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DECLARED: Apache-2.0 |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::python-dateutil:2.8.2'. Incompatibility of the Apache-2.0 license with the MPL-1.1 license is explicitly stated in the MPL-1.1 license checklist. How to fixRemove the dependency on 'PyPI::python-dateutil:2.8.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
170 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: Apache-2.0 |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::python-dateutil:2.8.2'. Incompatibility of the Apache-2.0 license with the MPL-1.1 license is explicitly stated in the MPL-1.1 license checklist. How to fixRemove the dependency on 'PyPI::python-dateutil:2.8.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
171 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: Python-2.0 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Python-2.0 of its dependency 'PyPI::python-dateutil:2.8.2'. Incompatibility of the Python-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. Interpretation: The requirement of the Python license to provide a brief summary of the changes may definitely be seen as a further restriction the final license prohibits to impose, since it requires to describe the changes rather than only to mention the fact that changes were made and such brief summary must be included in source code and binary delivery. However, another interpretation may argue that the final license requires at least disclosure, though not always inclusion, of the complete corresponding source code which enables a sufficiently well trained engineer to extract the differences, understand the changes and derive a summary which then would be, at least partly, in line with the Python license requirement. How to fixRemove the dependency on 'PyPI::python-dateutil:2.8.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
172 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DECLARED: Apache-2.0 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::requests:2.28.2'. Incompatibility of the Apache-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. How to fixRemove the dependency on 'PyPI::requests:2.28.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
173 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: Apache-2.0 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::requests:2.28.2'. Incompatibility of the Apache-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. How to fixRemove the dependency on 'PyPI::requests:2.28.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
174 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DECLARED: Apache-2.0 |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::requests:2.28.2'. Incompatibility of the Apache-2.0 license with the MPL-1.1 license is explicitly stated in the MPL-1.1 license checklist. How to fixRemove the dependency on 'PyPI::requests:2.28.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
175 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: Apache-2.0 |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::requests:2.28.2'. Incompatibility of the Apache-2.0 license with the MPL-1.1 license is explicitly stated in the MPL-1.1 license checklist. How to fixRemove the dependency on 'PyPI::requests:2.28.2' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
176 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: Apache-2.0 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::setuptools:67.6.1'. Incompatibility of the Apache-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. How to fixRemove the dependency on 'PyPI::setuptools:67.6.1' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
177 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: Apache-2.0 |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::setuptools:67.6.1'. Incompatibility of the Apache-2.0 license with the MPL-1.1 license is explicitly stated in the MPL-1.1 license checklist. How to fixRemove the dependency on 'PyPI::setuptools:67.6.1' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
178 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: GPL-3.0-only |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::setuptools:67.6.1'. 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.1' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
179 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: GPL-3.0-only |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::setuptools:67.6.1'. 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.1' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
180 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: GPL-3.0-only |
The outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::setuptools:67.6.1'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under another copyleft license such as the CPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::setuptools:67.6.1' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
181 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: GPL-3.0-only |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::setuptools:67.6.1'. 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.1' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
182 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: GPL-3.0-only |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::setuptools:67.6.1'. 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.1' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
183 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: GPL-3.0-only |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::setuptools:67.6.1'. Software under a copyleft license such as the GPL-3.0-only license normally cannot be redistributed under another copyleft license such as the GPL-1.0-or-later license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::setuptools:67.6.1' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
184 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: GPL-3.0-only |
The outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::setuptools:67.6.1'. 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.1' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
185 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: GPL-3.0-only |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license GPL-3.0-only of its dependency 'PyPI::setuptools:67.6.1'. 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-1.1 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::setuptools:67.6.1' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
186 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: MPL-2.0 |
The outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::setuptools:67.6.1'. 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.1' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
187 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: MPL-2.0 |
The outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::setuptools:67.6.1'. 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.1' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
188 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: MPL-2.0 |
The outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::setuptools:67.6.1'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under another copyleft license such as the CPL-1.0 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::setuptools:67.6.1' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
189 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: MPL-2.0 |
The outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::setuptools:67.6.1'. 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.1' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
190 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: MPL-2.0 |
The outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::setuptools:67.6.1'. 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.1' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
191 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: MPL-2.0 |
The outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::setuptools:67.6.1'. 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.1' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
192 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: MPL-2.0 |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license MPL-2.0 of its dependency 'PyPI::setuptools:67.6.1'. Software under a copyleft license such as the MPL-2.0 license normally cannot be redistributed under another copyleft license such as the MPL-1.1 license, except if it were explicitly permitted in the licenses. How to fixRemove the dependency on 'PyPI::setuptools:67.6.1' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
193 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: Python-2.0 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Python-2.0 of its dependency 'PyPI::setuptools:67.6.1'. Incompatibility of the Python-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. Interpretation: The requirement of the Python license to provide a brief summary of the changes may definitely be seen as a further restriction the final license prohibits to impose, since it requires to describe the changes rather than only to mention the fact that changes were made and such brief summary must be included in source code and binary delivery. However, another interpretation may argue that the final license requires at least disclosure, though not always inclusion, of the complete corresponding source code which enables a sufficiently well trained engineer to extract the differences, understand the changes and derive a summary which then would be, at least partly, in line with the Python license requirement. How to fixRemove the dependency on 'PyPI::setuptools:67.6.1' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
194 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tabulate:0.9.0 | DETECTED: Python-2.0 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Python-2.0 of its dependency 'PyPI::tabulate:0.9.0'. Incompatibility of the Python-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. Interpretation: The requirement of the Python license to provide a brief summary of the changes may definitely be seen as a further restriction the final license prohibits to impose, since it requires to describe the changes rather than only to mention the fact that changes were made and such brief summary must be included in source code and binary delivery. However, another interpretation may argue that the final license requires at least disclosure, though not always inclusion, of the complete corresponding source code which enables a sufficiently well trained engineer to extract the differences, understand the changes and derive a summary which then would be, at least partly, in line with the Python license requirement. How to fixRemove the dependency on 'PyPI::tabulate:0.9.0' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
195 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tomli:2.0.1 | DETECTED: Python-2.0 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Python-2.0 of its dependency 'PyPI::tomli:2.0.1'. Incompatibility of the Python-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. Interpretation: The requirement of the Python license to provide a brief summary of the changes may definitely be seen as a further restriction the final license prohibits to impose, since it requires to describe the changes rather than only to mention the fact that changes were made and such brief summary must be included in source code and binary delivery. However, another interpretation may argue that the final license requires at least disclosure, though not always inclusion, of the complete corresponding source code which enables a sufficiently well trained engineer to extract the differences, understand the changes and derive a summary which then would be, at least partly, in line with the Python license requirement. How to fixRemove the dependency on 'PyPI::tomli:2.0.1' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
196 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::typing-extensions:4.5.0 | DETECTED: Python-2.0 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Python-2.0 of its dependency 'PyPI::typing-extensions:4.5.0'. Incompatibility of the Python-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. Interpretation: The requirement of the Python license to provide a brief summary of the changes may definitely be seen as a further restriction the final license prohibits to impose, since it requires to describe the changes rather than only to mention the fact that changes were made and such brief summary must be included in source code and binary delivery. However, another interpretation may argue that the final license requires at least disclosure, though not always inclusion, of the complete corresponding source code which enables a sufficiently well trained engineer to extract the differences, understand the changes and derive a summary which then would be, at least partly, in line with the Python license requirement. How to fixRemove the dependency on 'PyPI::typing-extensions:4.5.0' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
197 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tzdata:2023.3 | DECLARED: Apache-2.0 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::tzdata:2023.3'. Incompatibility of the Apache-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. How to fixRemove the dependency on 'PyPI::tzdata:2023.3' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
198 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tzdata:2023.3 | DETECTED: Apache-2.0 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::tzdata:2023.3'. Incompatibility of the Apache-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. How to fixRemove the dependency on 'PyPI::tzdata:2023.3' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
199 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tzdata:2023.3 | DECLARED: Apache-2.0 |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::tzdata:2023.3'. Incompatibility of the Apache-2.0 license with the MPL-1.1 license is explicitly stated in the MPL-1.1 license checklist. How to fixRemove the dependency on 'PyPI::tzdata:2023.3' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
200 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tzdata:2023.3 | DETECTED: Apache-2.0 |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::tzdata:2023.3'. Incompatibility of the Apache-2.0 license with the MPL-1.1 license is explicitly stated in the MPL-1.1 license checklist. How to fixRemove the dependency on 'PyPI::tzdata:2023.3' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
201 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: Apache-2.0 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::urllib3:1.26.15'. Incompatibility of the Apache-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. How to fixRemove the dependency on 'PyPI::urllib3:1.26.15' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
202 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: Apache-2.0 |
The outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Apache-2.0 of its dependency 'PyPI::urllib3:1.26.15'. Incompatibility of the Apache-2.0 license with the MPL-1.1 license is explicitly stated in the MPL-1.1 license checklist. How to fixRemove the dependency on 'PyPI::urllib3:1.26.15' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
203 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: Python-2.0 |
The outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is incompatible with the inbound license Python-2.0 of its dependency 'PyPI::urllib3:1.26.15'. Incompatibility of the Python-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. Interpretation: The requirement of the Python license to provide a brief summary of the changes may definitely be seen as a further restriction the final license prohibits to impose, since it requires to describe the changes rather than only to mention the fact that changes were made and such brief summary must be included in source code and binary delivery. However, another interpretation may argue that the final license requires at least disclosure, though not always inclusion, of the complete corresponding source code which enables a sufficiently well trained engineer to extract the differences, understand the changes and derive a summary which then would be, at least partly, in line with the Python license requirement. How to fixRemove the dependency on 'PyPI::urllib3:1.26.15' or put 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' under a different license. |
204 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::argcomplete:3.0.5 | DECLARED: Apache-2.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::argcomplete:3.0.5'. There is insufficient information or knowledge whether the Apache-2.0 license is compatible with the CPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Apache-2.0 license with the CPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
205 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::argcomplete:3.0.5 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::argcomplete:3.0.5'. There is insufficient information or knowledge whether the Apache-2.0 license is compatible with the CPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Apache-2.0 license with the CPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
206 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::argcomplete:3.0.5 | DECLARED: Apache-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::argcomplete:3.0.5'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
207 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::argcomplete:3.0.5 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::argcomplete:3.0.5'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
208 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::argcomplete:3.0.5 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::argcomplete:3.0.5'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
209 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::argcomplete:3.0.5 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::argcomplete:3.0.5'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
210 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::argcomplete:3.0.5 | DETECTED: NOASSERTION |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::argcomplete:3.0.5'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
211 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::argcomplete:3.0.5 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::argcomplete:3.0.5'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
212 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::argcomplete:3.0.5 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::argcomplete:3.0.5'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
213 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::argcomplete:3.0.5 | DETECTED: NOASSERTION |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::argcomplete:3.0.5'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
214 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::argcomplete:3.0.5 | DETECTED: NOASSERTION |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::argcomplete:3.0.5'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
215 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::argcomplete:3.0.5 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::argcomplete:3.0.5'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
216 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::argcomplete:3.0.5 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::argcomplete:3.0.5'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
217 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DECLARED: LGPL-2.0-only |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.0-only of its dependency 'PyPI::astroid:2.15.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. |
218 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.0-only |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.0-only of its dependency 'PyPI::astroid:2.15.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. |
219 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DECLARED: LGPL-2.0-only |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.0-only of its dependency 'PyPI::astroid:2.15.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. |
220 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.0-only |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.0-only of its dependency 'PyPI::astroid:2.15.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. |
221 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DECLARED: LGPL-2.0-only |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.0-only of its dependency 'PyPI::astroid:2.15.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. |
222 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.0-only |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.0-only of its dependency 'PyPI::astroid:2.15.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. |
223 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DECLARED: LGPL-2.0-only |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.0-only of its dependency 'PyPI::astroid:2.15.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. |
224 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.0-only |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.0-only of its dependency 'PyPI::astroid:2.15.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. |
225 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DECLARED: LGPL-2.0-only |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.0-only of its dependency 'PyPI::astroid:2.15.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. |
226 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.0-only |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.0-only of its dependency 'PyPI::astroid:2.15.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. |
227 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DECLARED: LGPL-2.0-only |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.0-only of its dependency 'PyPI::astroid:2.15.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. |
228 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.0-only |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.0-only of its dependency 'PyPI::astroid:2.15.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. |
229 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DECLARED: LGPL-2.0-only |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.0-only of its dependency 'PyPI::astroid:2.15.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. |
230 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.0-only |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.0-only of its dependency 'PyPI::astroid:2.15.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. |
231 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DECLARED: LGPL-2.0-only |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.0-only of its dependency 'PyPI::astroid:2.15.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. |
232 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.0-only |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.0-only of its dependency 'PyPI::astroid:2.15.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. |
233 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DECLARED: LGPL-2.0-only |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.0-only of its dependency 'PyPI::astroid:2.15.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. |
234 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.0-only |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.0-only of its dependency 'PyPI::astroid:2.15.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. |
235 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::astroid:2.15.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. |
236 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::astroid:2.15.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. |
237 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::astroid:2.15.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. |
238 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::astroid:2.15.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. |
239 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::astroid:2.15.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. |
240 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::astroid:2.15.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. |
241 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::astroid:2.15.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. |
242 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::astroid:2.15.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. |
243 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.0-or-later of its dependency 'PyPI::astroid:2.15.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. |
244 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.1-only |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::astroid:2.15.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. |
245 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.1-only |
Whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::astroid:2.15.2' depends on the context. Depending compatibility of the LGPL-2.1-only license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
246 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DECLARED: LGPL-2.1-or-later |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::astroid:2.15.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. |
247 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.1-or-later |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::astroid:2.15.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. |
248 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DECLARED: LGPL-2.1-or-later |
Whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::astroid:2.15.2' depends on the context. Depending compatibility of the LGPL-2.1-or-later license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
249 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: LGPL-2.1-or-later |
Whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.1-or-later of its dependency 'PyPI::astroid:2.15.2' depends on the context. Depending compatibility of the LGPL-2.1-or-later license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
250 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::astroid:2.15.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. |
251 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::astroid:2.15.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. |
252 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::astroid:2.15.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. |
253 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::astroid:2.15.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. |
254 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::astroid:2.15.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. |
255 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::astroid:2.15.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. |
256 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::astroid:2.15.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. |
257 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::astroid:2.15.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. |
258 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::astroid:2.15.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::astroid:2.15.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. |
259 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::attrs:22.2.0 | DECLARED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::attrs:22.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. |
260 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::attrs:22.2.0 | DETECTED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::attrs:22.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. |
261 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::autopep8:2.0.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::autopep8:2.0.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. |
262 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::autopep8:2.0.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::autopep8:2.0.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. |
263 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::autopep8:2.0.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::autopep8:2.0.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. |
264 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::autopep8:2.0.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::autopep8:2.0.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. |
265 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::autopep8:2.0.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::autopep8:2.0.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. |
266 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::autopep8:2.0.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::autopep8:2.0.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. |
267 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::autopep8:2.0.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::autopep8:2.0.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. |
268 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::autopep8:2.0.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::autopep8:2.0.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. |
269 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::autopep8:2.0.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::autopep8:2.0.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. |
270 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::autopep8:2.0.2 | DECLARED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::autopep8:2.0.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. |
271 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::autopep8:2.0.2 | DETECTED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::autopep8:2.0.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. |
272 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DECLARED: MPL-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
273 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: MPL-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
274 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DECLARED: MPL-2.0 |
Whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MPL-2.0 of its dependency 'PyPI::certifi:2022.12.7' depends on the context. Depending compatibility of the MPL-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
275 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: MPL-2.0 |
Whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MPL-2.0 of its dependency 'PyPI::certifi:2022.12.7' depends on the context. Depending compatibility of the MPL-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
276 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: Python-2.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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 CPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the CPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
277 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
278 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
279 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: Python-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
280 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::certifi:2022.12.7 | DETECTED: Python-2.0 |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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-1.1 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the MPL-1.1 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
281 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
282 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
283 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: CC-BY-SA-3.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
284 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
285 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
286 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: CC-BY-SA-3.0 |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
287 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: CC-BY-SA-3.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
288 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
289 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: CC-BY-SA-3.0 |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
290 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LGPL-2.1-only |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
291 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LGPL-2.1-only |
Whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LGPL-2.1-only of its dependency 'PyPI::charset-normalizer:3.1.0' depends on the context. Depending compatibility of the LGPL-2.1-only license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
292 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
293 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
294 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
295 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
296 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
297 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
298 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
299 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
300 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
301 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DECLARED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
302 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
303 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: MPL-1.1 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
304 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
305 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
306 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
307 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
308 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
309 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
310 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
311 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
312 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::charset-normalizer:3.1.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
313 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DECLARED: Apache-2.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::coverage:7.2.3'. There is insufficient information or knowledge whether the Apache-2.0 license is compatible with the CPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Apache-2.0 license with the CPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
314 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::coverage:7.2.3'. There is insufficient information or knowledge whether the Apache-2.0 license is compatible with the CPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Apache-2.0 license with the CPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
315 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DECLARED: Apache-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::coverage:7.2.3'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
316 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::coverage:7.2.3'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
317 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: GPL-2.0-only |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license GPL-2.0-only of its dependency 'PyPI::coverage:7.2.3'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
318 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: LicenseRef-scancode-iso-8879 |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-iso-8879 of its dependency 'PyPI::coverage:7.2.3'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
319 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: LicenseRef-scancode-iso-8879 |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-iso-8879 of its dependency 'PyPI::coverage:7.2.3'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
320 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: LicenseRef-scancode-iso-8879 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-iso-8879 of its dependency 'PyPI::coverage:7.2.3'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
321 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: LicenseRef-scancode-iso-8879 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-iso-8879 of its dependency 'PyPI::coverage:7.2.3'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
322 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: LicenseRef-scancode-iso-8879 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-iso-8879 of its dependency 'PyPI::coverage:7.2.3'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
323 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: LicenseRef-scancode-iso-8879 |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-iso-8879 of its dependency 'PyPI::coverage:7.2.3'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
324 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: LicenseRef-scancode-iso-8879 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-iso-8879 of its dependency 'PyPI::coverage:7.2.3'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
325 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: LicenseRef-scancode-iso-8879 |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-iso-8879 of its dependency 'PyPI::coverage:7.2.3'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
326 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: LicenseRef-scancode-iso-8879 |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-iso-8879 of its dependency 'PyPI::coverage:7.2.3'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
327 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::coverage:7.2.3'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
328 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::coverage:7.2.3'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
329 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::coverage:7.2.3'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
330 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: NOASSERTION |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::coverage:7.2.3'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
331 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::coverage:7.2.3'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
332 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::coverage:7.2.3'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
333 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: NOASSERTION |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::coverage:7.2.3'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
334 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: NOASSERTION |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::coverage:7.2.3'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
335 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::coverage:7.2.3'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
336 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::coverage:7.2.3 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::coverage:7.2.3'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
337 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::datetime:5.1 | DECLARED: ZPL-2.1 |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::datetime:5.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. |
338 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::datetime:5.1 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::datetime:5.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. |
339 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::datetime:5.1 | DECLARED: ZPL-2.1 |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::datetime:5.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. |
340 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::datetime:5.1 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::datetime:5.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. |
341 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::datetime:5.1 | DECLARED: ZPL-2.1 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::datetime:5.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. |
342 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::datetime:5.1 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::datetime:5.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. |
343 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::datetime:5.1 | DECLARED: ZPL-2.1 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::datetime:5.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. |
344 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::datetime:5.1 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::datetime:5.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. |
345 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::datetime:5.1 | DECLARED: ZPL-2.1 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::datetime:5.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. |
346 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::datetime:5.1 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::datetime:5.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. |
347 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::datetime:5.1 | DECLARED: ZPL-2.1 |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::datetime:5.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. |
348 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::datetime:5.1 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::datetime:5.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. |
349 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::datetime:5.1 | DECLARED: ZPL-2.1 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::datetime:5.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. |
350 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::datetime:5.1 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::datetime:5.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. |
351 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::datetime:5.1 | DECLARED: ZPL-2.1 |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::datetime:5.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. |
352 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::datetime:5.1 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::datetime:5.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. |
353 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::datetime:5.1 | DECLARED: ZPL-2.1 |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::datetime:5.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. |
354 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::datetime:5.1 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::datetime:5.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. |
355 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::dill:0.3.6 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::dill:0.3.6'. There is insufficient information or knowledge whether the Apache-2.0 license is compatible with the CPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Apache-2.0 license with the CPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
356 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::dill:0.3.6 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::dill: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. |
357 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::dill:0.3.6 | DECLARED: BSD-3-Clause |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::dill: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. |
358 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::dill:0.3.6 | DETECTED: BSD-3-Clause |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::dill: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. |
359 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::dill:0.3.6 | DETECTED: DOC |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license DOC of its dependency 'PyPI::dill: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. |
360 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::dill:0.3.6 | DETECTED: DOC |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license DOC of its dependency 'PyPI::dill: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. |
361 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::dill:0.3.6 | DETECTED: DOC |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license DOC of its dependency 'PyPI::dill: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. |
362 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::dill:0.3.6 | DETECTED: DOC |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license DOC of its dependency 'PyPI::dill: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. |
363 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::dill:0.3.6 | DETECTED: DOC |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license DOC of its dependency 'PyPI::dill: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. |
364 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::dill:0.3.6 | DETECTED: DOC |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license DOC of its dependency 'PyPI::dill: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. |
365 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::dill:0.3.6 | DETECTED: DOC |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license DOC of its dependency 'PyPI::dill: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. |
366 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::dill:0.3.6 | DETECTED: DOC |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license DOC of its dependency 'PyPI::dill: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. |
367 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::dill:0.3.6 | DETECTED: DOC |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license DOC of its dependency 'PyPI::dill: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. |
368 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::dill:0.3.6 | DETECTED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::dill: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. |
369 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::dill:0.3.6 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::dill: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. |
370 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::dill:0.3.6 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::dill: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. |
371 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::dill:0.3.6 | DETECTED: NOASSERTION |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::dill: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. |
372 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::dill:0.3.6 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::dill: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. |
373 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::dill:0.3.6 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::dill: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. |
374 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::dill:0.3.6 | DETECTED: NOASSERTION |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::dill: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. |
375 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::dill:0.3.6 | DETECTED: NOASSERTION |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::dill: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. |
376 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::dill:0.3.6 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::dill: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. |
377 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::dill:0.3.6 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::dill: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. |
378 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::exceptiongroup:1.1.1 | DECLARED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::exceptiongroup:1.1.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. |
379 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::exceptiongroup:1.1.1 | DETECTED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::exceptiongroup:1.1.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. |
380 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::exceptiongroup:1.1.1 | DETECTED: Python-2.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::exceptiongroup:1.1.1'. There is insufficient information or knowledge whether the Python-2.0 license is compatible with the CPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the CPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
381 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::exceptiongroup:1.1.1 | DETECTED: Python-2.0 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::exceptiongroup:1.1.1'. 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. |
382 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::exceptiongroup:1.1.1 | DETECTED: Python-2.0 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::exceptiongroup:1.1.1'. 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. |
383 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::exceptiongroup:1.1.1 | DETECTED: Python-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::exceptiongroup:1.1.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. |
384 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::exceptiongroup:1.1.1 | DETECTED: Python-2.0 |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::exceptiongroup:1.1.1'. There is insufficient information or knowledge whether the Python-2.0 license is compatible with the MPL-1.1 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the MPL-1.1 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
385 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::idna:3.4 | DETECTED: BSD-3-Clause |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
386 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
387 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
388 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::idna:3.4 | DETECTED: LicenseRef-scancode-unicode |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
389 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
390 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
391 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::idna:3.4 | DETECTED: LicenseRef-scancode-unicode |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
392 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::idna:3.4 | DETECTED: LicenseRef-scancode-unicode |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
393 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
394 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::idna:3.4 | DETECTED: LicenseRef-scancode-unicode |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
395 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::iniconfig:2.0.0 | DECLARED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::iniconfig:2.0.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
396 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::iniconfig:2.0.0 | DETECTED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::iniconfig:2.0.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
397 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::isort:5.12.0 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::isort:5.12.0'. There is insufficient information or knowledge whether the Apache-2.0 license is compatible with the CPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Apache-2.0 license with the CPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
398 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::isort:5.12.0 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::isort:5.12.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
399 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::isort:5.12.0 | DETECTED: CC0-1.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC0-1.0 of its dependency 'PyPI::isort:5.12.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
400 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::isort:5.12.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::isort:5.12.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
401 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::isort:5.12.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::isort:5.12.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
402 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::isort:5.12.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::isort:5.12.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
403 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::isort:5.12.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::isort:5.12.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
404 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::isort:5.12.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::isort:5.12.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
405 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::isort:5.12.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::isort:5.12.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
406 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::isort:5.12.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::isort:5.12.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
407 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::isort:5.12.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::isort:5.12.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
408 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::isort:5.12.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::isort:5.12.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
409 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::isort:5.12.0 | DECLARED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::isort:5.12.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
410 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::isort:5.12.0 | DETECTED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::isort:5.12.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
411 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lazy-object-proxy:1.9.0 | DECLARED: BSD-2-Clause |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-2-Clause of its dependency 'PyPI::lazy-object-proxy:1.9.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
412 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lazy-object-proxy:1.9.0 | DETECTED: BSD-2-Clause |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-2-Clause of its dependency 'PyPI::lazy-object-proxy:1.9.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
413 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::lazy-object-proxy:1.9.0 | DETECTED: BSD-3-Clause |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::lazy-object-proxy:1.9.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
414 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::mccabe:0.7.0 | DECLARED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::mccabe:0.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. |
415 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::mccabe:0.7.0 | DETECTED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::mccabe:0.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. |
416 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::mccabe:0.7.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::mccabe:0.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. |
417 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::mccabe:0.7.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::mccabe:0.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. |
418 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::mccabe:0.7.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::mccabe:0.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. |
419 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::mccabe:0.7.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::mccabe:0.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. |
420 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::mccabe:0.7.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::mccabe:0.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. |
421 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::mccabe:0.7.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::mccabe:0.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. |
422 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::mccabe:0.7.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::mccabe:0.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. |
423 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::mccabe:0.7.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::mccabe:0.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. |
424 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::mccabe:0.7.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::mccabe:0.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. |
425 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::numpy:1.24.2'. There is insufficient information or knowledge whether the Apache-2.0 license is compatible with the CPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Apache-2.0 license with the CPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
426 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::numpy:1.24.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. |
427 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: BSD-2-Clause |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-2-Clause of its dependency 'PyPI::numpy:1.24.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. |
428 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: BSD-2-Clause-Views |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-2-Clause-Views of its dependency 'PyPI::numpy:1.24.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. |
429 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: BSD-2-Clause-Views |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-2-Clause-Views of its dependency 'PyPI::numpy:1.24.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. |
430 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: BSD-2-Clause-Views |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-2-Clause-Views of its dependency 'PyPI::numpy:1.24.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. |
431 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: BSD-2-Clause-Views |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-2-Clause-Views of its dependency 'PyPI::numpy:1.24.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. |
432 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: BSD-2-Clause-Views |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-2-Clause-Views of its dependency 'PyPI::numpy:1.24.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. |
433 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: BSD-2-Clause-Views |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-2-Clause-Views of its dependency 'PyPI::numpy:1.24.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. |
434 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: BSD-2-Clause-Views |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-2-Clause-Views of its dependency 'PyPI::numpy:1.24.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. |
435 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: BSD-2-Clause-Views |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-2-Clause-Views of its dependency 'PyPI::numpy:1.24.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. |
436 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: BSD-2-Clause-Views |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-2-Clause-Views of its dependency 'PyPI::numpy:1.24.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. |
437 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DECLARED: BSD-3-Clause |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::numpy:1.24.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. |
438 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: BSD-3-Clause |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::numpy:1.24.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. |
439 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: BSD-3-Clause-Open-MPI |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-3-Clause-Open-MPI of its dependency 'PyPI::numpy:1.24.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. |
440 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: BSD-3-Clause-Open-MPI |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-3-Clause-Open-MPI of its dependency 'PyPI::numpy:1.24.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. |
441 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: BSD-3-Clause-Open-MPI |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-3-Clause-Open-MPI of its dependency 'PyPI::numpy:1.24.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. |
442 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: BSD-3-Clause-Open-MPI |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-3-Clause-Open-MPI of its dependency 'PyPI::numpy:1.24.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. |
443 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: BSD-3-Clause-Open-MPI |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-3-Clause-Open-MPI of its dependency 'PyPI::numpy:1.24.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. |
444 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: BSD-3-Clause-Open-MPI |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-3-Clause-Open-MPI of its dependency 'PyPI::numpy:1.24.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. |
445 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: BSD-3-Clause-Open-MPI |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-3-Clause-Open-MPI of its dependency 'PyPI::numpy:1.24.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. |
446 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: BSD-3-Clause-Open-MPI |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-3-Clause-Open-MPI of its dependency 'PyPI::numpy:1.24.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. |
447 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: BSD-3-Clause-Open-MPI |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-3-Clause-Open-MPI of its dependency 'PyPI::numpy:1.24.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. |
448 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::numpy:1.24.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. |
449 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::numpy:1.24.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. |
450 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::numpy:1.24.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. |
451 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::numpy:1.24.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. |
452 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::numpy:1.24.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. |
453 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::numpy:1.24.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. |
454 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::numpy:1.24.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. |
455 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::numpy:1.24.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. |
456 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::numpy:1.24.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. |
457 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: CC-BY-SA-3.0 |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-SA-3.0 of its dependency 'PyPI::numpy:1.24.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. |
458 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: CC-BY-SA-3.0 |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-SA-3.0 of its dependency 'PyPI::numpy:1.24.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. |
459 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: CC-BY-SA-3.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-SA-3.0 of its dependency 'PyPI::numpy:1.24.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. |
460 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: CC-BY-SA-3.0 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-SA-3.0 of its dependency 'PyPI::numpy:1.24.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. |
461 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: CC-BY-SA-3.0 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-SA-3.0 of its dependency 'PyPI::numpy:1.24.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. |
462 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: CC-BY-SA-3.0 |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-SA-3.0 of its dependency 'PyPI::numpy:1.24.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. |
463 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: CC-BY-SA-3.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-SA-3.0 of its dependency 'PyPI::numpy:1.24.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. |
464 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: CC-BY-SA-3.0 |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-SA-3.0 of its dependency 'PyPI::numpy:1.24.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. |
465 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: CC-BY-SA-3.0 |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-SA-3.0 of its dependency 'PyPI::numpy:1.24.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. |
466 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: CC0-1.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC0-1.0 of its dependency 'PyPI::numpy:1.24.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. |
467 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: DOC |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license DOC of its dependency 'PyPI::numpy:1.24.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. |
468 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: DOC |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license DOC of its dependency 'PyPI::numpy:1.24.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. |
469 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: DOC |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license DOC of its dependency 'PyPI::numpy:1.24.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. |
470 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: DOC |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license DOC of its dependency 'PyPI::numpy:1.24.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. |
471 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: DOC |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license DOC of its dependency 'PyPI::numpy:1.24.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. |
472 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: DOC |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license DOC of its dependency 'PyPI::numpy:1.24.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. |
473 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: DOC |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license DOC of its dependency 'PyPI::numpy:1.24.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. |
474 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: DOC |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license DOC of its dependency 'PyPI::numpy:1.24.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. |
475 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: DOC |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license DOC of its dependency 'PyPI::numpy:1.24.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. |
476 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-only |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license GPL-3.0-only of its dependency 'PyPI::numpy:1.24.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. |
477 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-only WITH GCC-exception-3.1 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license GPL-3.0-only (simplified from 'GPL-3.0-only WITH GCC-exception-3.1') of its dependency 'PyPI::numpy:1.24.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. |
478 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-or-later |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license GPL-3.0-or-later of its dependency 'PyPI::numpy:1.24.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. |
479 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-or-later WITH GCC-exception-3.1 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license GPL-3.0-or-later (simplified from 'GPL-3.0-or-later WITH GCC-exception-3.1') of its dependency 'PyPI::numpy:1.24.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. |
480 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-bsla-no-advert |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-bsla-no-advert of its dependency 'PyPI::numpy:1.24.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. |
481 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-bsla-no-advert |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-bsla-no-advert of its dependency 'PyPI::numpy:1.24.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. |
482 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-bsla-no-advert |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-bsla-no-advert of its dependency 'PyPI::numpy:1.24.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. |
483 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-bsla-no-advert |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-bsla-no-advert of its dependency 'PyPI::numpy:1.24.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. |
484 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-bsla-no-advert |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-bsla-no-advert of its dependency 'PyPI::numpy:1.24.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. |
485 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-bsla-no-advert |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-bsla-no-advert of its dependency 'PyPI::numpy:1.24.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. |
486 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-bsla-no-advert |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-bsla-no-advert of its dependency 'PyPI::numpy:1.24.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. |
487 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-bsla-no-advert |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-bsla-no-advert of its dependency 'PyPI::numpy:1.24.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. |
488 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-bsla-no-advert |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-bsla-no-advert of its dependency 'PyPI::numpy:1.24.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. |
489 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::numpy:1.24.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. |
490 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::numpy:1.24.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. |
491 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::numpy:1.24.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. |
492 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::numpy:1.24.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. |
493 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::numpy:1.24.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. |
494 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::numpy:1.24.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. |
495 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::numpy:1.24.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. |
496 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::numpy:1.24.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. |
497 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-proprietary-license |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-proprietary-license of its dependency 'PyPI::numpy:1.24.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. |
498 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::numpy:1.24.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. |
499 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::numpy:1.24.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. |
500 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::numpy:1.24.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. |
501 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::numpy:1.24.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. |
502 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::numpy:1.24.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. |
503 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::numpy:1.24.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. |
504 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::numpy:1.24.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. |
505 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::numpy:1.24.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. |
506 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::numpy:1.24.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. |
507 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-sunpro |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-sunpro of its dependency 'PyPI::numpy:1.24.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. |
508 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-sunpro |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-sunpro of its dependency 'PyPI::numpy:1.24.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. |
509 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-sunpro |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-sunpro of its dependency 'PyPI::numpy:1.24.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. |
510 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-sunpro |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-sunpro of its dependency 'PyPI::numpy:1.24.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. |
511 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-sunpro |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-sunpro of its dependency 'PyPI::numpy:1.24.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. |
512 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-sunpro |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-sunpro of its dependency 'PyPI::numpy:1.24.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. |
513 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-sunpro |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-sunpro of its dependency 'PyPI::numpy:1.24.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. |
514 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-sunpro |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-sunpro of its dependency 'PyPI::numpy:1.24.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. |
515 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-sunpro |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-sunpro of its dependency 'PyPI::numpy:1.24.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. |
516 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::numpy:1.24.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. |
517 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: NCSA |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NCSA of its dependency 'PyPI::numpy:1.24.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. |
518 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: NCSA |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NCSA of its dependency 'PyPI::numpy:1.24.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. |
519 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: NCSA |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NCSA of its dependency 'PyPI::numpy:1.24.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. |
520 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: NCSA |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NCSA of its dependency 'PyPI::numpy:1.24.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. |
521 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: NCSA |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NCSA of its dependency 'PyPI::numpy:1.24.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. |
522 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: NCSA |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NCSA of its dependency 'PyPI::numpy:1.24.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. |
523 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: NCSA |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NCSA of its dependency 'PyPI::numpy:1.24.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. |
524 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: NCSA |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NCSA of its dependency 'PyPI::numpy:1.24.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. |
525 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: NCSA |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NCSA of its dependency 'PyPI::numpy:1.24.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. |
526 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::numpy:1.24.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. |
527 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::numpy:1.24.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. |
528 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::numpy:1.24.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. |
529 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::numpy:1.24.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. |
530 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::numpy:1.24.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. |
531 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::numpy:1.24.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. |
532 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::numpy:1.24.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. |
533 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::numpy:1.24.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. |
534 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::numpy:1.24.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. |
535 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: Unlicense |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Unlicense of its dependency 'PyPI::numpy:1.24.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. |
536 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::numpy:1.24.2 | DETECTED: Zlib |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Zlib of its dependency 'PyPI::numpy:1.24.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. |
537 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::packaging:23.0 | DECLARED: Apache-2.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::packaging:23.0'. There is insufficient information or knowledge whether the Apache-2.0 license is compatible with the CPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Apache-2.0 license with the CPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
538 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::packaging:23.0 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::packaging:23.0'. There is insufficient information or knowledge whether the Apache-2.0 license is compatible with the CPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Apache-2.0 license with the CPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
539 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::packaging:23.0 | DECLARED: Apache-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::packaging:23.0'. 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::packaging:23.0 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::packaging:23.0'. 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::packaging:23.0 | DETECTED: BSD-2-Clause |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-2-Clause of its dependency 'PyPI::packaging:23.0'. 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::packaging:23.0 | DETECTED: BSD-3-Clause |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::packaging:23.0'. 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::pandas:2.0.0 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::pandas:2.0.0'. There is insufficient information or knowledge whether the Apache-2.0 license is compatible with the CPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Apache-2.0 license with the CPL-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::pandas:2.0.0 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::pandas:2.0.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
545 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pandas:2.0.0 | DETECTED: BSD-2-Clause |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-2-Clause of its dependency 'PyPI::pandas:2.0.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
546 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pandas:2.0.0 | DETECTED: BSD-3-Clause |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: LicenseRef-scancode-mit-nagy |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-mit-nagy of its dependency 'PyPI::pandas:2.0.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
548 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pandas:2.0.0 | DETECTED: LicenseRef-scancode-mit-nagy |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-mit-nagy of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: LicenseRef-scancode-mit-nagy |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-mit-nagy of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: LicenseRef-scancode-mit-nagy |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-mit-nagy of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: LicenseRef-scancode-mit-nagy |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-mit-nagy of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: LicenseRef-scancode-mit-nagy |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-mit-nagy of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: LicenseRef-scancode-mit-nagy |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-mit-nagy of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: LicenseRef-scancode-mit-nagy |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-mit-nagy of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: LicenseRef-scancode-mit-nagy |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-mit-nagy of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: MPL-1.1 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MPL-1.1 of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: MPL-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MPL-2.0 of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: MPL-2.0 |
Whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MPL-2.0 of its dependency 'PyPI::pandas:2.0.0' depends on the context. Depending compatibility of the MPL-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
569 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pandas:2.0.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: Python-2.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::pandas:2.0.0'. There is insufficient information or knowledge whether the Python-2.0 license is compatible with the CPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the CPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
579 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pandas:2.0.0 | DETECTED: Python-2.0 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::pandas:2.0.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. |
580 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pandas:2.0.0 | DETECTED: Python-2.0 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::pandas:2.0.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. |
581 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pandas:2.0.0 | DETECTED: Python-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::pandas:2.0.0'. 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::pandas:2.0.0 | DETECTED: Python-2.0 |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::pandas:2.0.0'. There is insufficient information or knowledge whether the Python-2.0 license is compatible with the MPL-1.1 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the MPL-1.1 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
583 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::platformdirs:3.2.0 | DECLARED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
584 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::platformdirs:3.2.0 | DETECTED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
585 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pluggy:1.0.0 | DECLARED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::pluggy:1.0.0'. 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::pluggy:1.0.0 | DETECTED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::pluggy:1.0.0'. 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::pycodestyle:2.10.0 | DECLARED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::pycodestyle:2.10.0'. 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::pycodestyle:2.10.0 | DETECTED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::pycodestyle:2.10.0'. 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::pycodestyle:2.10.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pycodestyle:2.10.0'. 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::pycodestyle:2.10.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pycodestyle:2.10.0'. 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::pycodestyle:2.10.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pycodestyle:2.10.0'. 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::pycodestyle:2.10.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pycodestyle:2.10.0'. 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::pycodestyle:2.10.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pycodestyle:2.10.0'. 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::pycodestyle:2.10.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pycodestyle:2.10.0'. 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::pycodestyle:2.10.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pycodestyle:2.10.0'. 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::pycodestyle:2.10.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pycodestyle:2.10.0'. 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::pycodestyle:2.10.0 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pycodestyle:2.10.0'. 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::pylint:2.17.2 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::pylint:2.17.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. |
599 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::pylint:2.17.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. |
600 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::pylint:2.17.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. |
601 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::pylint:2.17.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. |
602 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::pylint:2.17.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. |
603 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::pylint:2.17.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. |
604 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::pylint:2.17.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. |
605 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::pylint:2.17.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. |
606 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: CC-BY-4.0 |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-4.0 of its dependency 'PyPI::pylint:2.17.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. |
607 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: CC-BY-SA-4.0 |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-SA-4.0 of its dependency 'PyPI::pylint:2.17.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. |
608 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: CC-BY-SA-4.0 |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-SA-4.0 of its dependency 'PyPI::pylint:2.17.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. |
609 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: CC-BY-SA-4.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-SA-4.0 of its dependency 'PyPI::pylint:2.17.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. |
610 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: CC-BY-SA-4.0 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-SA-4.0 of its dependency 'PyPI::pylint:2.17.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. |
611 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: CC-BY-SA-4.0 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-SA-4.0 of its dependency 'PyPI::pylint:2.17.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. |
612 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: CC-BY-SA-4.0 |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-SA-4.0 of its dependency 'PyPI::pylint:2.17.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. |
613 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: CC-BY-SA-4.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-SA-4.0 of its dependency 'PyPI::pylint:2.17.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. |
614 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: CC-BY-SA-4.0 |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-SA-4.0 of its dependency 'PyPI::pylint:2.17.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. |
615 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: CC-BY-SA-4.0 |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license CC-BY-SA-4.0 of its dependency 'PyPI::pylint:2.17.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. |
616 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: GPL-1.0-or-later |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license GPL-1.0-or-later of its dependency 'PyPI::pylint:2.17.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. |
617 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DECLARED: GPL-2.0-only |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pylint:2.17.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. |
618 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: GPL-2.0-only |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license GPL-2.0-only of its dependency 'PyPI::pylint:2.17.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. |
619 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DECLARED: GPL-2.0-or-later |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pylint:2.17.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. |
620 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: GPL-2.0-or-later |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license GPL-2.0-or-later of its dependency 'PyPI::pylint:2.17.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. |
621 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::pylint:2.17.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. |
622 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pylint:2.17.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. |
623 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pylint:2.17.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. |
624 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pylint:2.17.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. |
625 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pylint:2.17.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. |
626 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pylint:2.17.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. |
627 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pylint:2.17.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. |
628 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pylint:2.17.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. |
629 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pylint:2.17.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. |
630 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pylint:2.17.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pylint:2.17.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. |
631 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pytest:7.2.2 | DETECTED: JSON |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license JSON of its dependency 'PyPI::pytest:7.2.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. |
632 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pytest:7.2.2 | DETECTED: JSON |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license JSON of its dependency 'PyPI::pytest:7.2.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. |
633 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pytest:7.2.2 | DETECTED: JSON |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license JSON of its dependency 'PyPI::pytest:7.2.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. |
634 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pytest:7.2.2 | DETECTED: JSON |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license JSON of its dependency 'PyPI::pytest:7.2.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. |
635 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pytest:7.2.2 | DETECTED: JSON |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license JSON of its dependency 'PyPI::pytest:7.2.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. |
636 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pytest:7.2.2 | DETECTED: JSON |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license JSON of its dependency 'PyPI::pytest:7.2.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. |
637 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pytest:7.2.2 | DETECTED: JSON |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license JSON of its dependency 'PyPI::pytest:7.2.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. |
638 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pytest:7.2.2 | DETECTED: JSON |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license JSON of its dependency 'PyPI::pytest:7.2.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. |
639 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pytest:7.2.2 | DETECTED: JSON |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license JSON of its dependency 'PyPI::pytest:7.2.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. |
640 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pytest:7.2.2 | DECLARED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::pytest:7.2.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. |
641 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pytest:7.2.2 | DETECTED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::pytest:7.2.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. |
642 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pytest:7.2.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pytest:7.2.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. |
643 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pytest:7.2.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pytest:7.2.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. |
644 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pytest:7.2.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pytest:7.2.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. |
645 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pytest:7.2.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pytest:7.2.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. |
646 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pytest:7.2.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pytest:7.2.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. |
647 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pytest:7.2.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pytest:7.2.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. |
648 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pytest:7.2.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pytest:7.2.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. |
649 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pytest:7.2.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pytest:7.2.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. |
650 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pytest:7.2.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::pytest:7.2.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. |
651 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pytest-cov:4.0.0 | DECLARED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::pytest-cov:4.0.0'. 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::pytest-cov:4.0.0 | DETECTED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::pytest-cov:4.0.0'. 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::python-dateutil:2.8.2 | DECLARED: Apache-2.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::python-dateutil:2.8.2'. There is insufficient information or knowledge whether the Apache-2.0 license is compatible with the CPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Apache-2.0 license with the CPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
654 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::python-dateutil:2.8.2'. There is insufficient information or knowledge whether the Apache-2.0 license is compatible with the CPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Apache-2.0 license with the CPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
655 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DECLARED: Apache-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
656 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
657 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: BSD-2-Clause |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
658 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: BSD-3-Clause |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
659 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
660 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
661 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
662 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
663 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
664 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
665 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
666 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
667 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
668 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: Python-2.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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 CPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the CPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
669 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
670 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
671 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: Python-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
672 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::python-dateutil:2.8.2 | DETECTED: Python-2.0 |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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-1.1 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the MPL-1.1 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
673 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pytz:2023.3 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pytz:2023.3'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
674 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::pytz:2023.3 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pytz:2023.3'. 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::pytz:2023.3 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pytz:2023.3'. 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::pytz:2023.3 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pytz:2023.3'. 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::pytz:2023.3 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pytz:2023.3'. 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::pytz:2023.3 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pytz:2023.3'. 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::pytz:2023.3 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pytz:2023.3'. 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::pytz:2023.3 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pytz:2023.3'. 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::pytz:2023.3 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::pytz:2023.3'. 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::pytz:2023.3 | DECLARED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::pytz:2023.3'. 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::pytz:2023.3 | DETECTED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::pytz:2023.3'. 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::pytz:2023.3 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::pytz:2023.3'. 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::pytz:2023.3 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::pytz:2023.3'. 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::pytz:2023.3 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::pytz:2023.3'. 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::pytz:2023.3 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::pytz:2023.3'. 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::pytz:2023.3 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::pytz:2023.3'. 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::pytz:2023.3 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::pytz:2023.3'. 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::pytz:2023.3 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::pytz:2023.3'. 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::pytz:2023.3 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::pytz:2023.3'. 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::pytz:2023.3 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::pytz:2023.3'. 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::requests:2.28.2 | DECLARED: Apache-2.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::requests:2.28.2'. There is insufficient information or knowledge whether the Apache-2.0 license is compatible with the CPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Apache-2.0 license with the CPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
694 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::requests:2.28.2'. There is insufficient information or knowledge whether the Apache-2.0 license is compatible with the CPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Apache-2.0 license with the CPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
695 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DECLARED: Apache-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
696 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
697 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: BSD-2-Clause |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
698 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: BSD-3-Clause |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
699 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: ISC |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
700 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
701 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
702 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
703 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
704 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
705 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
706 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
707 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
708 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: LGPL-2.0-or-later |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
709 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
710 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
711 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
712 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
713 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
714 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
715 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
716 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
717 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
718 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::requests:2.28.2 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
719 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::setuptools:67.6.1'. There is insufficient information or knowledge whether the Apache-2.0 license is compatible with the CPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Apache-2.0 license with the CPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
720 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::setuptools:67.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. |
721 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: BSD-2-Clause |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-2-Clause of its dependency 'PyPI::setuptools:67.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. |
722 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: BSD-3-Clause |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::setuptools:67.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. |
723 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: GPL-3.0-only |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license GPL-3.0-only of its dependency 'PyPI::setuptools:67.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. |
724 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DECLARED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::setuptools:67.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. |
725 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::setuptools:67.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. |
726 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: MPL-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MPL-2.0 of its dependency 'PyPI::setuptools:67.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. |
727 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: MPL-2.0 |
Whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MPL-2.0 of its dependency 'PyPI::setuptools:67.6.1' depends on the context. Depending compatibility of the MPL-2.0 license with the GPL-1.0-or-later license is explicitly stated in the GPL-1.0-or-later license checklist. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
728 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: NOASSERTION |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::setuptools:67.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. |
729 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: NOASSERTION |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::setuptools:67.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. |
730 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: NOASSERTION |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::setuptools:67.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. |
731 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::setuptools:67.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. |
732 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: NOASSERTION |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::setuptools:67.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. |
733 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: NOASSERTION |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::setuptools:67.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. |
734 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: NOASSERTION |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::setuptools:67.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. |
735 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::setuptools:67.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. |
736 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: NOASSERTION |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license NOASSERTION of its dependency 'PyPI::setuptools:67.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. |
737 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: Python-2.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::setuptools:67.6.1'. There is insufficient information or knowledge whether the Python-2.0 license is compatible with the CPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the CPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
738 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: Python-2.0 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::setuptools:67.6.1'. 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. |
739 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: Python-2.0 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::setuptools:67.6.1'. 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. |
740 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: Python-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::setuptools:67.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. |
741 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::setuptools:67.6.1 | DETECTED: Python-2.0 |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::setuptools:67.6.1'. There is insufficient information or knowledge whether the Python-2.0 license is compatible with the MPL-1.1 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the MPL-1.1 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
742 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::six:1.16.0 | DECLARED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
743 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::six:1.16.0 | DETECTED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
744 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tabulate:0.9.0 | DECLARED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::tabulate:0.9.0'. 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::tabulate:0.9.0 | DETECTED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::tabulate:0.9.0'. 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::tabulate:0.9.0 | DETECTED: Python-2.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::tabulate:0.9.0'. There is insufficient information or knowledge whether the Python-2.0 license is compatible with the CPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the CPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
747 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tabulate:0.9.0 | DETECTED: Python-2.0 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::tabulate:0.9.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. |
748 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tabulate:0.9.0 | DETECTED: Python-2.0 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::tabulate:0.9.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. |
749 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tabulate:0.9.0 | DETECTED: Python-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::tabulate:0.9.0'. 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::tabulate:0.9.0 | DETECTED: Python-2.0 |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::tabulate:0.9.0'. There is insufficient information or knowledge whether the Python-2.0 license is compatible with the MPL-1.1 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the MPL-1.1 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
751 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::termcolor:2.2.0 | DECLARED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::termcolor:2.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. |
752 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::termcolor:2.2.0 | DETECTED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::termcolor:2.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. |
753 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tomli:2.0.1 | DECLARED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::tomli:2.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. |
754 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tomli:2.0.1 | DETECTED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::tomli:2.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. |
755 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tomli:2.0.1 | DETECTED: Python-2.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::tomli:2.0.1'. There is insufficient information or knowledge whether the Python-2.0 license is compatible with the CPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the CPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
756 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tomli:2.0.1 | DETECTED: Python-2.0 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::tomli:2.0.1'. 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. |
757 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tomli:2.0.1 | DETECTED: Python-2.0 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::tomli:2.0.1'. 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. |
758 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tomli:2.0.1 | DETECTED: Python-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::tomli:2.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. |
759 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tomli:2.0.1 | DETECTED: Python-2.0 |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::tomli:2.0.1'. There is insufficient information or knowledge whether the Python-2.0 license is compatible with the MPL-1.1 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the MPL-1.1 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
760 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tomlkit:0.11.7 | DETECTED: ISC |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ISC of its dependency 'PyPI::tomlkit:0.11.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. |
761 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tomlkit:0.11.7 | DECLARED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::tomlkit:0.11.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. |
762 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tomlkit:0.11.7 | DETECTED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license MIT of its dependency 'PyPI::tomlkit:0.11.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. |
763 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::typing-extensions:4.5.0 | DECLARED: PSF-2.0 |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license PSF-2.0 of its dependency 'PyPI::typing-extensions:4.5.0'. 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::typing-extensions:4.5.0 | DECLARED: PSF-2.0 |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license PSF-2.0 of its dependency 'PyPI::typing-extensions:4.5.0'. 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::typing-extensions:4.5.0 | DECLARED: PSF-2.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license PSF-2.0 of its dependency 'PyPI::typing-extensions:4.5.0'. 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::typing-extensions:4.5.0 | DECLARED: PSF-2.0 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license PSF-2.0 of its dependency 'PyPI::typing-extensions:4.5.0'. 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::typing-extensions:4.5.0 | DECLARED: PSF-2.0 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license PSF-2.0 of its dependency 'PyPI::typing-extensions:4.5.0'. 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::typing-extensions:4.5.0 | DECLARED: PSF-2.0 |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license PSF-2.0 of its dependency 'PyPI::typing-extensions:4.5.0'. 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::typing-extensions:4.5.0 | DECLARED: PSF-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license PSF-2.0 of its dependency 'PyPI::typing-extensions:4.5.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
770 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::typing-extensions:4.5.0 | DECLARED: PSF-2.0 |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license PSF-2.0 of its dependency 'PyPI::typing-extensions:4.5.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
771 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::typing-extensions:4.5.0 | DECLARED: PSF-2.0 |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license PSF-2.0 of its dependency 'PyPI::typing-extensions:4.5.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
772 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::typing-extensions:4.5.0 | DETECTED: Python-2.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::typing-extensions:4.5.0'. There is insufficient information or knowledge whether the Python-2.0 license is compatible with the CPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the CPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
773 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::typing-extensions:4.5.0 | DETECTED: Python-2.0 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::typing-extensions:4.5.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. |
774 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::typing-extensions:4.5.0 | DETECTED: Python-2.0 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::typing-extensions:4.5.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. |
775 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::typing-extensions:4.5.0 | DETECTED: Python-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::typing-extensions:4.5.0'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
776 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::typing-extensions:4.5.0 | DETECTED: Python-2.0 |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Python-2.0 of its dependency 'PyPI::typing-extensions:4.5.0'. There is insufficient information or knowledge whether the Python-2.0 license is compatible with the MPL-1.1 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the MPL-1.1 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
777 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tzdata:2023.3 | DECLARED: Apache-2.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::tzdata:2023.3'. There is insufficient information or knowledge whether the Apache-2.0 license is compatible with the CPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Apache-2.0 license with the CPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
778 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tzdata:2023.3 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::tzdata:2023.3'. There is insufficient information or knowledge whether the Apache-2.0 license is compatible with the CPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Apache-2.0 license with the CPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
779 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tzdata:2023.3 | DECLARED: Apache-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::tzdata:2023.3'. 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::tzdata:2023.3 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::tzdata:2023.3'. 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::tzdata:2023.3 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::tzdata:2023.3'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
782 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tzdata:2023.3 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::tzdata:2023.3'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
783 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tzdata:2023.3 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::tzdata:2023.3'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
784 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tzdata:2023.3 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::tzdata:2023.3'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
785 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tzdata:2023.3 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::tzdata:2023.3'. 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::tzdata:2023.3 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::tzdata:2023.3'. This combination of licenses is not covered by the compliance matrix. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
787 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::tzdata:2023.3 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::tzdata:2023.3'. 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::tzdata:2023.3 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::tzdata:2023.3'. 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::tzdata:2023.3 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license LicenseRef-scancode-public-domain of its dependency 'PyPI::tzdata:2023.3'. 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::urllib3:1.26.15 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license Apache-2.0 of its dependency 'PyPI::urllib3:1.26.15'. There is insufficient information or knowledge whether the Apache-2.0 license is compatible with the CPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Apache-2.0 license with the CPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
791 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: Apache-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
792 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
793 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
794 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
795 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
796 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
797 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
798 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
799 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
800 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: LicenseRef-scancode-public-domain |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
801 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DECLARED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
802 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: MIT |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
803 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: Python-2.0 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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 CPL-1.0 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the CPL-1.0 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
804 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
805 | 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:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
806 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: Python-2.0 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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. |
807 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::urllib3:1.26.15 | DETECTED: Python-2.0 |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' 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-1.1 license or not. Therefore, a general recommendation on the compatibility of the Python-2.0 license with the MPL-1.1 license cannot be given. How to fixGet legal advice and eventually create a (global) rule violation resolution. |
808 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::wrapt:1.15.0 | DETECTED: BSD-2-Clause |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-2-Clause of its dependency 'PyPI::wrapt:1.15.0'. 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::wrapt:1.15.0 | DECLARED: BSD-3-Clause |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::wrapt:1.15.0'. 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::wrapt:1.15.0 | DETECTED: BSD-3-Clause |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license BSD-3-Clause of its dependency 'PyPI::wrapt:1.15.0'. 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::zope-interface:6.0 | DECLARED: ZPL-2.1 |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::zope-interface: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. |
812 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::zope-interface:6.0 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license Apache-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::zope-interface: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. |
813 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::zope-interface:6.0 | DECLARED: ZPL-2.1 |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::zope-interface: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. |
814 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::zope-interface:6.0 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license BSD-3-Clause of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::zope-interface: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. |
815 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::zope-interface:6.0 | DECLARED: ZPL-2.1 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::zope-interface: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. |
816 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::zope-interface:6.0 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license CPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::zope-interface: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. |
817 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::zope-interface:6.0 | DECLARED: ZPL-2.1 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::zope-interface: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. |
818 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::zope-interface:6.0 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license EPL-1.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::zope-interface: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. |
819 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::zope-interface:6.0 | DECLARED: ZPL-2.1 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::zope-interface: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. |
820 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::zope-interface:6.0 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license EPL-2.0 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::zope-interface: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. |
821 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::zope-interface:6.0 | DECLARED: ZPL-2.1 |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::zope-interface: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. |
822 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::zope-interface:6.0 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::zope-interface: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. |
823 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::zope-interface:6.0 | DECLARED: ZPL-2.1 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::zope-interface: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. |
824 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::zope-interface:6.0 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::zope-interface: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. |
825 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::zope-interface:6.0 | DECLARED: ZPL-2.1 |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::zope-interface: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. |
826 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::zope-interface:6.0 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license MIT of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::zope-interface: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. |
827 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::zope-interface:6.0 | DECLARED: ZPL-2.1 |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::zope-interface: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. |
828 | OSADL_PROJECT_LICENSE_COMPATIBILITY | PyPI::zope-interface:6.0 | DETECTED: ZPL-2.1 |
It is unknown whether the outbound license MPL-1.1 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is compatible with the inbound license ZPL-2.1 of its dependency 'PyPI::zope-interface: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. |
829 | DEPENDENCY_LICENSE_CHECK | PyPI::argcomplete:3.0.5 | DETECTED: NOASSERTION |
License NOASSERTION of dependency 'PyPI::argcomplete:3.0.5' is unclassified. How to fixClassify NOASSERTION as either approved or restricted. |
830 | DEPENDENCY_LICENSE_CHECK | PyPI::astroid:2.15.2 | DETECTED: NOASSERTION |
License NOASSERTION of dependency 'PyPI::astroid:2.15.2' is unclassified. How to fixClassify NOASSERTION as either approved or restricted. |
831 | DEPENDENCY_LICENSE_CHECK | PyPI::autopep8:2.0.2 | DETECTED: LicenseRef-scancode-public-domain |
License LicenseRef-scancode-public-domain of dependency 'PyPI::autopep8:2.0.2' is unclassified. How to fixClassify LicenseRef-scancode-public-domain as either approved or restricted. |
832 | 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. |
833 | 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. |
834 | 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. |
835 | DEPENDENCY_LICENSE_CHECK | PyPI::coverage:7.2.3 | DETECTED: GPL-2.0-only |
License GPL-2.0-only of dependency 'PyPI::coverage:7.2.3' is unclassified. How to fixClassify GPL-2.0-only as either approved or restricted. |
836 | DEPENDENCY_LICENSE_CHECK | PyPI::coverage:7.2.3 | DETECTED: LicenseRef-scancode-iso-8879 |
License LicenseRef-scancode-iso-8879 of dependency 'PyPI::coverage:7.2.3' is unclassified. How to fixClassify LicenseRef-scancode-iso-8879 as either approved or restricted. |
837 | DEPENDENCY_LICENSE_CHECK | PyPI::coverage:7.2.3 | DETECTED: NOASSERTION |
License NOASSERTION of dependency 'PyPI::coverage:7.2.3' is unclassified. How to fixClassify NOASSERTION as either approved or restricted. |
838 | DEPENDENCY_LICENSE_CHECK | PyPI::dill:0.3.6 | DETECTED: DOC |
License DOC of dependency 'PyPI::dill:0.3.6' is unclassified. How to fixClassify DOC as either approved or restricted. |
839 | DEPENDENCY_LICENSE_CHECK | PyPI::dill:0.3.6 | DETECTED: NOASSERTION |
License NOASSERTION of dependency 'PyPI::dill:0.3.6' is unclassified. How to fixClassify NOASSERTION as either approved or restricted. |
840 | DEPENDENCY_LICENSE_CHECK | PyPI::exceptiongroup:1.1.1 | DETECTED: Python-2.0 |
License Python-2.0 of dependency 'PyPI::exceptiongroup:1.1.1' is unclassified. How to fixClassify Python-2.0 as either approved or restricted. |
841 | 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. |
842 | DEPENDENCY_LICENSE_CHECK | PyPI::isort:5.12.0 | DETECTED: LicenseRef-scancode-public-domain |
License LicenseRef-scancode-public-domain of dependency 'PyPI::isort:5.12.0' is unclassified. How to fixClassify LicenseRef-scancode-public-domain as either approved or restricted. |
843 | DEPENDENCY_LICENSE_CHECK | PyPI::mccabe:0.7.0 | DETECTED: NOASSERTION |
License NOASSERTION of dependency 'PyPI::mccabe:0.7.0' is unclassified. How to fixClassify NOASSERTION as either approved or restricted. |
844 | DEPENDENCY_LICENSE_CHECK | PyPI::numpy:1.24.2 | DETECTED: BSD-3-Clause-Open-MPI |
License BSD-3-Clause-Open-MPI of dependency 'PyPI::numpy:1.24.2' is unclassified. How to fixClassify BSD-3-Clause-Open-MPI as either approved or restricted. |
845 | DEPENDENCY_LICENSE_CHECK | PyPI::numpy:1.24.2 | DETECTED: DOC |
License DOC of dependency 'PyPI::numpy:1.24.2' is unclassified. How to fixClassify DOC as either approved or restricted. |
846 | DEPENDENCY_LICENSE_CHECK | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-only |
License GPL-3.0-only of dependency 'PyPI::numpy:1.24.2' is unclassified. How to fixClassify GPL-3.0-only as either approved or restricted. |
847 | DEPENDENCY_LICENSE_CHECK | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-only WITH GCC-exception-3.1 |
License GPL-3.0-only WITH GCC-exception-3.1 of dependency 'PyPI::numpy:1.24.2' is unclassified. How to fixClassify GPL-3.0-only WITH GCC-exception-3.1 as either approved or restricted. |
848 | DEPENDENCY_LICENSE_CHECK | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-or-later |
License GPL-3.0-or-later of dependency 'PyPI::numpy:1.24.2' is unclassified. How to fixClassify GPL-3.0-or-later as either approved or restricted. |
849 | DEPENDENCY_LICENSE_CHECK | PyPI::numpy:1.24.2 | DETECTED: GPL-3.0-or-later WITH GCC-exception-3.1 |
License GPL-3.0-or-later WITH GCC-exception-3.1 of dependency 'PyPI::numpy:1.24.2' is unclassified. How to fixClassify GPL-3.0-or-later WITH GCC-exception-3.1 as either approved or restricted. |
850 | DEPENDENCY_LICENSE_CHECK | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-bsla-no-advert |
License LicenseRef-scancode-bsla-no-advert of dependency 'PyPI::numpy:1.24.2' is unclassified. How to fixClassify LicenseRef-scancode-bsla-no-advert as either approved or restricted. |
851 | DEPENDENCY_LICENSE_CHECK | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-proprietary-license |
License LicenseRef-scancode-proprietary-license of dependency 'PyPI::numpy:1.24.2' is unclassified. How to fixClassify LicenseRef-scancode-proprietary-license as either approved or restricted. |
852 | DEPENDENCY_LICENSE_CHECK | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-public-domain |
License LicenseRef-scancode-public-domain of dependency 'PyPI::numpy:1.24.2' is unclassified. How to fixClassify LicenseRef-scancode-public-domain as either approved or restricted. |
853 | DEPENDENCY_LICENSE_CHECK | PyPI::numpy:1.24.2 | DETECTED: LicenseRef-scancode-sunpro |
License LicenseRef-scancode-sunpro of dependency 'PyPI::numpy:1.24.2' is unclassified. How to fixClassify LicenseRef-scancode-sunpro as either approved or restricted. |
854 | DEPENDENCY_LICENSE_CHECK | PyPI::numpy:1.24.2 | DETECTED: NCSA |
License NCSA of dependency 'PyPI::numpy:1.24.2' is unclassified. How to fixClassify NCSA as either approved or restricted. |
855 | DEPENDENCY_LICENSE_CHECK | PyPI::numpy:1.24.2 | DETECTED: NOASSERTION |
License NOASSERTION of dependency 'PyPI::numpy:1.24.2' is unclassified. How to fixClassify NOASSERTION as either approved or restricted. |
856 | DEPENDENCY_LICENSE_CHECK | PyPI::numpy:1.24.2 | DETECTED: Unlicense |
License Unlicense of dependency 'PyPI::numpy:1.24.2' is unclassified. How to fixClassify Unlicense as either approved or restricted. |
857 | DEPENDENCY_LICENSE_CHECK | PyPI::pandas:2.0.0 | DETECTED: LicenseRef-scancode-mit-nagy |
License LicenseRef-scancode-mit-nagy of dependency 'PyPI::pandas:2.0.0' is unclassified. How to fixClassify LicenseRef-scancode-mit-nagy as either approved or restricted. |
858 | DEPENDENCY_LICENSE_CHECK | PyPI::pandas:2.0.0 | DETECTED: LicenseRef-scancode-public-domain |
License LicenseRef-scancode-public-domain of dependency 'PyPI::pandas:2.0.0' is unclassified. How to fixClassify LicenseRef-scancode-public-domain as either approved or restricted. |
859 | DEPENDENCY_LICENSE_CHECK | PyPI::pandas:2.0.0 | DETECTED: NOASSERTION |
License NOASSERTION of dependency 'PyPI::pandas:2.0.0' is unclassified. How to fixClassify NOASSERTION as either approved or restricted. |
860 | DEPENDENCY_LICENSE_CHECK | PyPI::pandas:2.0.0 | DETECTED: Python-2.0 |
License Python-2.0 of dependency 'PyPI::pandas:2.0.0' is unclassified. How to fixClassify Python-2.0 as either approved or restricted. |
861 | DEPENDENCY_LICENSE_CHECK | PyPI::pycodestyle:2.10.0 | DETECTED: NOASSERTION |
License NOASSERTION of dependency 'PyPI::pycodestyle:2.10.0' is unclassified. How to fixClassify NOASSERTION as either approved or restricted. |
862 | DEPENDENCY_LICENSE_CHECK | PyPI::pylint:2.17.2 | DETECTED: GPL-1.0-or-later |
License GPL-1.0-or-later of dependency 'PyPI::pylint:2.17.2' is unclassified. How to fixClassify GPL-1.0-or-later as either approved or restricted. |
863 | DEPENDENCY_LICENSE_CHECK | PyPI::pylint:2.17.2 | DECLARED: GPL-2.0-only |
License GPL-2.0-only of dependency 'PyPI::pylint:2.17.2' is unclassified. How to fixClassify GPL-2.0-only as either approved or restricted. |
864 | DEPENDENCY_LICENSE_CHECK | PyPI::pylint:2.17.2 | DETECTED: GPL-2.0-only |
License GPL-2.0-only of dependency 'PyPI::pylint:2.17.2' is unclassified. How to fixClassify GPL-2.0-only as either approved or restricted. |
865 | DEPENDENCY_LICENSE_CHECK | PyPI::pylint:2.17.2 | DECLARED: GPL-2.0-or-later |
License GPL-2.0-or-later of dependency 'PyPI::pylint:2.17.2' is unclassified. How to fixClassify GPL-2.0-or-later as either approved or restricted. |
866 | DEPENDENCY_LICENSE_CHECK | PyPI::pylint:2.17.2 | DETECTED: GPL-2.0-or-later |
License GPL-2.0-or-later of dependency 'PyPI::pylint:2.17.2' is unclassified. How to fixClassify GPL-2.0-or-later as either approved or restricted. |
867 | DEPENDENCY_LICENSE_CHECK | PyPI::pylint:2.17.2 | DETECTED: NOASSERTION |
License NOASSERTION of dependency 'PyPI::pylint:2.17.2' is unclassified. How to fixClassify NOASSERTION as either approved or restricted. |
868 | DEPENDENCY_LICENSE_CHECK | PyPI::pytest:7.2.2 | DETECTED: NOASSERTION |
License NOASSERTION of dependency 'PyPI::pytest:7.2.2' is unclassified. How to fixClassify NOASSERTION as either approved or restricted. |
869 | 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. |
870 | 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. |
871 | DEPENDENCY_LICENSE_CHECK | PyPI::pytz:2023.3 | DETECTED: LicenseRef-scancode-public-domain |
License LicenseRef-scancode-public-domain of dependency 'PyPI::pytz:2023.3' is unclassified. How to fixClassify LicenseRef-scancode-public-domain as either approved or restricted. |
872 | 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. |
873 | DEPENDENCY_LICENSE_CHECK | PyPI::setuptools:67.6.1 | DETECTED: GPL-3.0-only |
License GPL-3.0-only of dependency 'PyPI::setuptools:67.6.1' is unclassified. How to fixClassify GPL-3.0-only as either approved or restricted. |
874 | DEPENDENCY_LICENSE_CHECK | PyPI::setuptools:67.6.1 | DETECTED: NOASSERTION |
License NOASSERTION of dependency 'PyPI::setuptools:67.6.1' is unclassified. How to fixClassify NOASSERTION as either approved or restricted. |
875 | DEPENDENCY_LICENSE_CHECK | PyPI::setuptools:67.6.1 | DETECTED: Python-2.0 |
License Python-2.0 of dependency 'PyPI::setuptools:67.6.1' is unclassified. How to fixClassify Python-2.0 as either approved or restricted. |
876 | DEPENDENCY_LICENSE_CHECK | PyPI::tabulate:0.9.0 | DETECTED: Python-2.0 |
License Python-2.0 of dependency 'PyPI::tabulate:0.9.0' is unclassified. How to fixClassify Python-2.0 as either approved or restricted. |
877 | DEPENDENCY_LICENSE_CHECK | PyPI::tomli:2.0.1 | DETECTED: Python-2.0 |
License Python-2.0 of dependency 'PyPI::tomli:2.0.1' is unclassified. How to fixClassify Python-2.0 as either approved or restricted. |
878 | DEPENDENCY_LICENSE_CHECK | PyPI::typing-extensions:4.5.0 | DECLARED: PSF-2.0 |
License PSF-2.0 of dependency 'PyPI::typing-extensions:4.5.0' is unclassified. How to fixClassify PSF-2.0 as either approved or restricted. |
879 | DEPENDENCY_LICENSE_CHECK | PyPI::typing-extensions:4.5.0 | DETECTED: Python-2.0 |
License Python-2.0 of dependency 'PyPI::typing-extensions:4.5.0' is unclassified. How to fixClassify Python-2.0 as either approved or restricted. |
880 | DEPENDENCY_LICENSE_CHECK | PyPI::tzdata:2023.3 | DETECTED: LicenseRef-scancode-public-domain |
License LicenseRef-scancode-public-domain of dependency 'PyPI::tzdata:2023.3' is unclassified. How to fixClassify LicenseRef-scancode-public-domain as either approved or restricted. |
881 | 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. |
882 | 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. |
883 | PROJECT_LICENSE_CHECK | PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06 | DETECTED: GPL-1.0-or-later |
License GPL-1.0-or-later of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is unclassified. How to fixClassify GPL-1.0-or-later as either approved or restricted. |
884 | PROJECT_LICENSE_CHECK | PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06 | DETECTED: LicenseRef-scancode-eclipse-sua-2017 |
License LicenseRef-scancode-eclipse-sua-2017 of project 'PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06' is unclassified. How to fixClassify LicenseRef-scancode-eclipse-sua-2017 as either approved or restricted. |
Type | Git |
URL | https://github.com/eclipse-cdt-cloud/tsp-python-client.git |
Path | |
Revision | db9f94eae6d4dc01e59288b7934c4a98e24d2e06 |
# | Package | Scopes | Licenses | Analyzer Issues | Scanner Issues |
---|---|---|---|---|---|
1 | PIP::requirements.txt:db9f94eae6d4dc01e59288b7934c4a98e24d2e06 | Detected Licenses (from VCS):
|
|
|
|
2 | PyPI::argcomplete:3.0.5 |
|
Declared Licenses:
|
|
|
3 | PyPI::astroid:2.15.2 |
|
Declared Licenses:
|
|
|
4 | PyPI::attrs:22.2.0 |
|
Declared Licenses: |
|
|
5 | PyPI::autopep8:2.0.2 |
|
Declared Licenses:
|
|
|
6 | PyPI::certifi:2022.12.7 |
|
Declared Licenses:
|
|
|
7 | PyPI::charset-normalizer:3.1.0 |
|
Declared Licenses:
|
|
|
8 | PyPI::coverage:7.2.3 |
|
Declared Licenses:
|
|
|
9 | PyPI::coverage[toml]:7.2.3 |
|
|
|
|
10 | PyPI::datetime:5.1 |
|
Declared Licenses: |
|
|
11 | PyPI::dill:0.3.6 |
|
Declared Licenses:
|
|
|
12 | PyPI::exceptiongroup:1.1.1 |
|
Declared Licenses:
|
|
|
13 | PyPI::idna:3.4 |
|
Detected Licenses (from VCS):
|
|
|
14 | PyPI::iniconfig:2.0.0 |
|
Declared Licenses: |
|
|
15 | PyPI::isort:5.12.0 |
|
Declared Licenses:
|
|
|
16 | PyPI::lazy-object-proxy:1.9.0 |
|
Declared Licenses:
|
|
|
17 | PyPI::mccabe:0.7.0 |
|
Declared Licenses:
|
|
|
18 | PyPI::numpy:1.24.2 |
|
Declared Licenses:
|
|
|
19 | PyPI::packaging:23.0 |
|
Declared Licenses:
|
|
|
20 | PyPI::pandas:2.0.0 |
|
Detected Licenses (from artifact):
|
|
|
21 | PyPI::platformdirs:3.2.0 |
|
Declared Licenses: |
|
|
22 | PyPI::pluggy:1.0.0 |
|
Declared Licenses: |
|
|
23 | PyPI::pycodestyle:2.10.0 |
|
Declared Licenses:
|
|
|
24 | PyPI::pylint:2.17.2 |
|
Declared Licenses:
|
|
|
25 | PyPI::pytest:7.2.2 |
|
Declared Licenses:
|
|
|
26 | PyPI::pytest-cov:4.0.0 |
|
Declared Licenses: |
|
|
27 | PyPI::python-dateutil:2.8.2 |
|
Declared Licenses:
|
|
|
28 | PyPI::pytz:2023.3 |
|
Declared Licenses:
|
|
|
29 | PyPI::requests:2.28.2 |
|
Declared Licenses:
|
|
|
30 | PyPI::setuptools:67.6.1 |
|
Declared Licenses:
|
|
|
31 | PyPI::six:1.16.0 |
|
Declared Licenses: |
|
|
32 | PyPI::tabulate:0.9.0 |
|
Declared Licenses:
|
|
|
33 | PyPI::termcolor:2.2.0 |
|
Declared Licenses: |
|
|
34 | PyPI::tomli:2.0.1 |
|
Declared Licenses:
|
|
|
35 | PyPI::tomlkit:0.11.7 |
|
Declared Licenses: |
|
|
36 | PyPI::typing-extensions:4.5.0 |
|
Declared Licenses:
|
|
|
37 | PyPI::tzdata:2023.3 |
|
Declared Licenses:
|
|
|
38 | PyPI::urllib3:1.26.15 |
|
Declared Licenses:
|
|
|
39 | PyPI::wrapt:1.15.0 |
|
Declared Licenses:
|
|
|
40 | PyPI::zope-interface:6.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."