aboutcode-org / aboutcode-org/scancode-toolkit

Detection finds `google-patent-license-golang` in Polymer license text

Offen
#3,907 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
bug
Vorherrschende Sprache
Python
Sterne
2.6k
Forks
791
Ø Merge
1 T. 12 Std.
Gemergte PRs (30 T.)
5

Beschreibung

The license text found in plenty of NPM packages, e.g. [^1], is detected as `BSD-3-Clause AND LicenseRef-scancode-google-patent-license-golang`. This is wrong, because the actual license text is `google-patent-license` plus some polymer specific header, while `google-patent-license-golang = google-patent-license + some Golang specific header`.

ScanCode has the following variations of the google patent license,
whereas licenses IDs with a suffix after `google-patent-license` contain `google-patent-license` plus some header:
- https://scancode-licensedb.aboutcode.org/google-patent-license-fuchsia.html
- https://scancode-licensedb.aboutcode.org/google-patent-license-golang.html
- https://scancode-licensedb.aboutcode.org/google-patent-license-webm.html
- https://scancode-licensedb.aboutcode.org/google-patent-license-webrtc.html
- https://scancode-licensedb.aboutcode.org/google-patent-license.html

Proposed solution:
- preferred: Add a new license ID: `google-patent-license-polymer`
- alternative: Change the detection to detect `BSD-3-Clause AND LicenseRef-scancode-google-patent-license`.

[^1]: https://github.com/PolymerElements/iron-a11y-keys-behavior/blob/ebfffaf7bd630ba43b7cff143d5c25d5e55e14bd/iron-a11y-keys-behavior.js#L2-L9

Beitragsleitfaden

Beitragsleitfaden öffnen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.