aboutcode-org / aboutcode-org/scancode-toolkit

Validate all license-digger licenses are correctly detected

オープン
#4,141 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る
主要言語
Python
スター
2.6k
フォーク
791
平均マージ
1日 12時間
マージ済み PR(30日)
5

説明

We should add as test files most of the files from KDE's license-digger originally by @cordlandwehr @kossebau and team.
- The repo is at https://invent.kde.org/sdk/licensedigger with a mirror at https://github.com/KDE/licensedigger/
- Attached is a subset of the repo with files we should test: license text, templates and test suites. This is a nice data set as there is a lot of manual curation work that went into to review all and every license headers in the many project of KDE. See [licensedigger-master-cc4b24d3fb67afa8fb0a9ef61210588958eaf0f5.zip](https://github.com/user-attachments/files/18749172/licensedigger-master-cc4b24d3fb67afa8fb0a9ef61210588958eaf0f5.zip)

I am fairly confident that we do detect all these, but we need to verify this, and we need highly accurate detection.

- Any license file text that is detected exactly by a matcher as a whole file or fragment should not be added as test, as this would be redundant.
- When a license text is detected approximately, this would be a candidate for rule addition.

コントリビューションガイド

コントリビューションガイドを開く

評価

この issue はまだ評価されていません。

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。