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
There is little to no logging in place as well as no intermediate results and it is therefore hard to understand how a package declared_license has been detected in a license_expression. We should potentially keep all the same intermediate results as we have in regular license detection as a diagnostic option, and while this may seem verbose this would be essential to track issues.
The text was updated successfully, but these errors were encountered:
pombredanne
changed the title
Improve tracing of license detection in package manifests
Package license data structure: Improve tracing of license detection in package manifests
Aug 20, 2021
Improve License Detection reporting #3286
We now have the entire license detection objects with the matches (with file origin info) for detections in package manifests. so this is completely traceable. Closing!
There is little to no logging in place as well as no intermediate results and it is therefore hard to understand how a package
declared_license
has been detected in alicense_expression
. We should potentially keep all the same intermediate results as we have in regular license detection as a diagnostic option, and while this may seem verbose this would be essential to track issues.The text was updated successfully, but these errors were encountered: