-
-
Notifications
You must be signed in to change notification settings - Fork 580
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
Detection rule needed for "3-Clause BSD License" #3069
Comments
This is already fixed in the LicenseDetection branch for the upcoming release: https://github.com/nexB/scancode-toolkit/tree/add-license-detection. How this is solved: Issue 1
Let me paste a sample example of how a LicenseDetection of the text Here
Issue 2There was also another issue present in this example (which is another type of license issue we are solving): The Here it was License scan results for the package when scanned from the LicenseDetection branch:
|
Attaching the full scan results here: |
A scan using
scancode-toolkit-31.0.2
oftomviz-2.0.0-rc1
tomviz-2.0.0-rc1-results.json.zip
( available from https://github.com/OpenChemistry/tomviz/archive/refs/tags/2.0.0-rc1.tar.gz )
returned the correct Declared license of bsd-new from the project LICENSE file, but it returned 425 instances of unknown-license-reference from files that contained the following string:
It is released under the 3-Clause BSD License, see "LICENSE". */
For example, the string can be found in file
tomviz-2.0.0-rc1/tests/cxx/AcquisitionClientTest.cxx
Since "3-Clause BSD License" is an obvious reference to bsd-new, this problem can probably be fixed with an addition or modification to the license detection rules.
Scan results attached.
The text was updated successfully, but these errors were encountered: