aboutcode-org / aboutcode-org/scancode-toolkit

Provide data values in scan results to correspond with license_clarity_score elements

未關閉
#1,395 2 則留言 0 個 reaction 已指派 1 人 已被 @swastkk 認領 在 GitHub 檢視
enhancement GSoC license_clarity_score
主要語言
Python
星號
2.6k
分支
791
平均合併
1 天 12 小時
30 天內合併 PR
5

描述

scancode-toolkit now provides a new `license_clarity_score` for example:
```
"license_clarity_score": {
"score": 77,
"has_declared_license_in_key_files": true,
"file_level_license_and_copyright_coverage": 0.1,
"has_consistent_key_and_file_level_licenses": true,
"is_using_only_spdx_licenses": true,
"has_full_text_for_all_licenses": true
},
```
The primary score element in question is ` "has_declared_license_in_key_files"` .
When this element is true, the big question the reader of the scan results will want to ask is what is that `declared_license`? Although scancode returns a list of all the detected licenses in the code that was scanned, I am not aware that it identifies which of those licenses (or license expressions) corresponds to the `declared_license`. It would be tremendoulsy helpful to see that in the scancode results, since it would tell the reader what the primary license (or license expression) of the software code (package) should be. Since scancode has obviously already found that information, in order to set the element to true, it makes sense to present that in the results.

It is possible that the other scoring elements might benefit from a similar improvement, but the `declared_license` seems to be the most important, and would provide the greatest value.

貢獻指南

開啟貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。