-
Notifications
You must be signed in to change notification settings - Fork 188
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
license-expression does not handle invalid license key characters #1199
Comments
I opened an issue for this with the license-expression library: aboutcode-org/license-expression#76 I will create a workaround for this in the meantime. |
rnjudge
changed the title
Update to license-expression causes bug when generating SPDX reports
license-expression does not handle invalid license key characters
Dec 15, 2022
rnjudge
added a commit
to rnjudge/tern
that referenced
this issue
Dec 15, 2022
When a license is reported with invalid license keys (i.e. anything besides letters and numbers, underscore, dot, colon or hyphen signs and spaces) the `is_spdx_license_expression()` function fails because the liense-expression library does not properly handle the unknown characters. This commit is a workaround until the issue opened in the license-expression library[1] is resolved. Resolves tern-tools#1199 [1] aboutcode-org/license-expression#76 Signed-off-by: Rose Judge <[email protected]>
rnjudge
added a commit
that referenced
this issue
Dec 15, 2022
When a license is reported with invalid license keys (i.e. anything besides letters and numbers, underscore, dot, colon or hyphen signs and spaces) the `is_spdx_license_expression()` function fails because the liense-expression library does not properly handle the unknown characters. This commit is a workaround until the issue opened in the license-expression library[1] is resolved. Resolves #1199 [1] aboutcode-org/license-expression#76 Signed-off-by: Rose Judge <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When a license is reported with invalid license keys (i.e. anything besides letters and numbers, underscore, dot, colon or hyphen signs and spaces) the
is_spdx_license_expression()
function fails because the liense-expression library fails to handle the error.To Reproduce
tern report -i debian:latest -f spdxtagvalue -o debian.spdx
Error in terminal
Expected behavior
SPDX report should be generated.
The text was updated successfully, but these errors were encountered: