-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add licence type to Nuget Package #92
Comments
brantburnett
added a commit
that referenced
this issue
Jan 23, 2024
The COPYING.txt file, which was ported from the original C++ implementation, appears to be the basic BSD-3-Clause license except for the parts about the testdata. However, the testdata is not included in the NuGet package so isn't relevant. Update the NuGet copyright to match the copyright notice in COPYING.txt. Also embed the README.md file in the package. Fixes #92
brantburnett
added a commit
that referenced
this issue
Jan 23, 2024
…#93) The COPYING.txt file, which was ported from the original C++ implementation, appears to be the basic BSD-3-Clause license except for the parts about the testdata. However, the testdata is not included in the NuGet package so isn't relevant. Update the NuGet copyright to match the copyright notice in COPYING.txt. Also embed the README.md file in the package. Fixes #92
Thanks for pointing this out. I've switched to using an SPDX instead of embedding the text in the NuGet, this is releasing shortly as 1.1.5. |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Is your feature request related to a problem? Please describe.
In dependency track this package is reporting as not having a licence type specified
Describe the solution you'd like
The PackageLicenseExpression property is set in the csproj so that the NUGET package has the information. This can then be included in the SBOM so that analysis can occur in the appropriate tools
Describe alternatives you've considered
Ignore them, bundle licence file into package & reference the file.
Additional context
N:a
The text was updated successfully, but these errors were encountered: