You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We never include the actual texts of a matched license, only the license matched text. This could be a mere notice or reference and not a full text. To automate attribution notice creation, it would be useful to have also all the license texts and extra details.
Therefore I suggest we had a new --license-reference option that would work such that a license_references scan-level attribute (as opposed to file-level) is added to the scan results and would contain a sorted list of the License object as available in the license data (both the .yml and the .LICENSE data)
The text was updated successfully, but these errors were encountered:
The new --licenses-reference option adds a new "licenses_reference" top
level attribute to a scan seen in the JSON and YAML attribute. This
contains all the license details.
Also bump the WIP version.
Reference: #1697
Signed-off-by: Philippe Ombredanne <[email protected]>
Description
We never include the actual texts of a matched license, only the license matched text. This could be a mere notice or reference and not a full text. To automate attribution notice creation, it would be useful to have also all the license texts and extra details.
Therefore I suggest we had a new
--license-reference
option that would work such that alicense_references
scan-level attribute (as opposed to file-level) is added to the scan results and would contain a sorted list of theLicense
object as available in the license data (both the .yml and the .LICENSE data)The text was updated successfully, but these errors were encountered: