-
-
Notifications
You must be signed in to change notification settings - Fork 577
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong SPDX license key for "llvm-exception" #2873
Comments
ScanCode reports exceptions to licenses as individual license findings. This is problematic as exceptions on their own are not valid SPDX expressions, also see [1]. Introduce a new function that fixes up findings by associating exceptions to their belonging licenses, for now at the example of "LLVM-exception" which by definition [2] always belongs to "Apache-2.0". [1]: aboutcode-org/scancode-toolkit#2873 [2]: https://spdx.org/licenses/LLVM-exception.html Signed-off-by: Sebastian Schuberth <[email protected]>
ScanCode reports exceptions to licenses as individual license findings. This is problematic as exceptions on their own are not valid SPDX expressions, also see [1]. Introduce a new function that fixes up findings by associating exceptions to their belonging licenses, for now at the example of "LLVM-exception" which by definition [2] always belongs to "Apache-2.0". [1]: aboutcode-org/scancode-toolkit#2873 [2]: https://spdx.org/licenses/LLVM-exception.html Signed-off-by: Sebastian Schuberth <[email protected]>
ScanCode reports exceptions to licenses as individual license findings. This is problematic as exceptions on their own are not valid SPDX expressions, also see [1]. Introduce a new function that fixes up findings by associating exceptions to their belonging licenses, for now at the example of "LLVM-exception" which by definition [2] always belongs to "Apache-2.0". [1]: aboutcode-org/scancode-toolkit#2873 [2]: https://spdx.org/licenses/LLVM-exception.html Signed-off-by: Sebastian Schuberth <[email protected]>
ScanCode reports exceptions to licenses as individual license findings. This is problematic as exceptions on their own are not valid SPDX expressions, also see [1]. Introduce a new function that fixes up findings by associating exceptions to their belonging licenses, for now at the example of "LLVM-exception" which by definition [2] always belongs to "Apache-2.0". [1]: aboutcode-org/scancode-toolkit#2873 [2]: https://spdx.org/licenses/LLVM-exception.html Signed-off-by: Sebastian Schuberth <[email protected]>
ScanCode reports exceptions to licenses as individual license findings. This is problematic as exceptions on their own are not valid SPDX expressions, also see [1]. Introduce a new function that fixes up findings by associating exceptions to their belonging licenses, for now at the example of "LLVM-exception" which by definition [2] always belongs to "Apache-2.0". [1]: aboutcode-org/scancode-toolkit#2873 [2]: https://spdx.org/licenses/LLVM-exception.html Signed-off-by: Sebastian Schuberth <[email protected]>
ScanCode reports exceptions to licenses as individual license findings. This is problematic as exceptions on their own are not valid SPDX expressions, also see [1]. Introduce a new function that fixes up findings by associating exceptions to their belonging licenses, for now at the example of "LLVM-exception" which by definition [2] always belongs to "Apache-2.0". [1]: aboutcode-org/scancode-toolkit#2873 [2]: https://spdx.org/licenses/LLVM-exception.html Signed-off-by: Sebastian Schuberth <[email protected]>
ScanCode reports exceptions to licenses as individual license findings. This is problematic as exceptions on their own are not valid SPDX expressions, also see [1]. Introduce a new function that fixes up findings by associating exceptions to their belonging licenses, for now at the example of "LLVM-exception" which by definition [2] always belongs to "Apache-2.0". [1]: aboutcode-org/scancode-toolkit#2873 [2]: https://spdx.org/licenses/LLVM-exception.html Signed-off-by: Sebastian Schuberth <[email protected]>
ScanCode reports exceptions to licenses as individual license findings. This is problematic as exceptions on their own are not valid SPDX expressions, also see [1]. Introduce a new function that fixes up findings by associating exceptions to their belonging licenses, for now at the example of "LLVM-exception" which by definition [2] always belongs to "Apache-2.0". [1]: aboutcode-org/scancode-toolkit#2873 [2]: https://spdx.org/licenses/LLVM-exception.html Signed-off-by: Sebastian Schuberth <[email protected]>
ScanCode reports exceptions to licenses as individual license findings. This is problematic as exceptions on their own are not valid SPDX expressions, also see [1]. Introduce a new function that fixes up findings by associating exceptions to their belonging licenses, for now at the example of "LLVM-exception" which by definition [2] always belongs to "Apache-2.0". [1]: aboutcode-org/scancode-toolkit#2873 [2]: https://spdx.org/licenses/LLVM-exception.html Signed-off-by: Sebastian Schuberth <[email protected]>
ScanCode reports exceptions to licenses as individual license findings. This is problematic as exceptions on their own are not valid SPDX expressions, also see [1]. Introduce a new function that fixes up findings by associating exceptions to their belonging licenses, for now at the example of "LLVM-exception" which by definition [2] always belongs to "Apache-2.0". [1]: aboutcode-org/scancode-toolkit#2873 [2]: https://spdx.org/licenses/LLVM-exception.html Signed-off-by: Sebastian Schuberth <[email protected]>
ScanCode reports exceptions to licenses as individual license findings. This is problematic as exceptions on their own are not valid SPDX expressions, also see [1]. Introduce a new function that fixes up findings by associating exceptions to their belonging licenses, for now at the example of "LLVM-exception" which by definition [2] always belongs to "Apache-2.0". [1]: aboutcode-org/scancode-toolkit#2873 [2]: https://spdx.org/licenses/LLVM-exception.html Signed-off-by: Sebastian Schuberth <[email protected]>
E.g. ScanCode reports exceptions to licenses as individual license findings. That is problematic as exceptions on their own are not valid SPDX expressions, also see [1]. Introduce a new function that fixes up findings by associating exceptions by their belonging licenses. [1]: aboutcode-org/scancode-toolkit#2873 Signed-off-by: Sebastian Schuberth <[email protected]>
E.g. ScanCode reports exceptions to licenses as individual license findings. That is problematic as exceptions on their own are not valid SPDX expressions, also see [1]. Introduce a new function that fixes up findings by associating exceptions by their belonging licenses. [1]: aboutcode-org/scancode-toolkit#2873 Signed-off-by: Sebastian Schuberth <[email protected]>
@sschuberth what you are saying is that https://github.com/bytecodealliance/wasi/blob/9ec04a7d8ebb1bbb9e3291503425cee1ec38a560/LICENSE-Apache-2.0_WITH_LLVM-exception should be detected as an |
Reference: #2873 Reported-by: Sebastian Schuberth <[email protected]> Signed-off-by: Philippe Ombredanne <[email protected]>
Correct. That's why in ORT we now have https://github.com/oss-review-toolkit/ort/blob/main/utils/spdx/src/main/resources/exception-mapping.yml.
Absolutely!
We do maintain the score as of oss-review-toolkit/ort#5131. |
👍 Thanks! |
Description
ScanCode translates its own license
key
"llvm-exception" tospdx_license_key
"LLVM-exception". However, as exceptions in SPDX expressions always have to come together with a license followed by theWITH
keyword, and as the LLVM exception always applies to Apache-2.0 only (AFAIK), thespdx_license_key
should be "Apache-2.0 WITH LLVM-exception" instead.Edit: I just realized that the
spdx_license_key
is probably not supposed to contain full SPDX expressions for historic reasons, but instead thelicense_expressions
should be used, which currently gets set toThere are two problems in here:
How To Reproduce
Download e.g. https://crates.io/api/v1/crates/wasi/0.10.2+wasi-snapshot-preview1/download and unpack the tarball. Scan it with
scancode --license --json-pp scancode.json .
which givesSystem configuration
The text was updated successfully, but these errors were encountered: