[QUESTION] Bug or feature - "licensed under the" triggers OSL-3.0 rule

Offen
  • Stimmt etwas nicht?
#5,347 3 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 3 Tagen

@Anurag-S1ngh arbeitet bereits daran.

Seit 31.10.2026.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
45/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
python
Bereich
search

Rechercherichtung

Start by reading the referenced OSL rule files, osl-3.0_54.RULE and osl-3.0_26.RULE, and investigate how ScanCode applies their matching rules to the examples in the issue. Check existing tests for license-rule matching and add or update coverage for generic license wording versus genuine OSL references. Done means the Katex example no longer produces a false OSL-3.0 detection while valid OSL matches remain detectable.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

I ran into this one using ClearlyDefined. I chose to open the issue here as I think it is closer to Scandcode than to CD.

The project Katex's README says:

KaTeX is licensed under the [MIT License](https://opensource.org/licenses/MIT).

The three words "licensed under the" trigger the osl.3.0_54.RULE, according to CD's API response

"license_detections": [
{
"license_expression": "osl-3.0 AND mit",
"license_expression_spdx": "OSL-3.0 AND MIT",
"matches": [
{
"license_expression": "osl-3.0",
"license_expression_spdx": "OSL-3.0",
"from_file": "cd--1-2FprPcto73nv/package/dist/README.md",
"start_line": 123,
"end_line": 125,
"matcher": "3-seq",
"score": 52.94,
"matched_length": 9,
"match_coverage": 52.94,
"rule_relevance": 100,
"rule_identifier": "osl-3.0_54.RULE",
"rule_url": "https://github.com/nexB/scancode-toolkit/tree/develop/src/licensedcode/data/rules/osl-3.0_54.RULE",
"matched_text": "## License\n\nKaTeX is licensed under the [MIT License](https://opensource.org/licenses/MIT).",
"matched_text_diagnostics": "License\n\n[KaTeX] [is] licensed under the [[MIT] License](https://opensource.org/licenses/"
}

Question: Is this intended? I mean, "licensed under the" is a very generic statement. Would every component which states that it is "licensed under the <enter_name_of_license_here>" trigger this OSL-3.0 rule?

Similar example:

"the full text of the license" triggers osl-3.0_26.RULE, for the aws-sdk-go-v2

https://github.com/aws/aws-sdk-go-v2/blob/main/service/lambda/api_op_PublishLayerVersion.go#L69

// The layer's software license. It can be any of the following:
	//
	//   - An [SPDX license identifier]. For example, MIT .
	//
	//   - The URL of a license hosted on the internet. For example,
	//   https://opensource.org/licenses/MIT .
	//
	//   - The full text of the license.
	//
	// [SPDX license identifier]: https://spdx.org/licenses/
	LicenseInfo *string

vs.

https://github.com/aboutcode-org/scancode-toolkit/blob/develop/src/licensedcode/data/rules/osl-3.0_26.RULE#L12

# This software is licensed under the Open Software License version
# 3.0. The full text of this license can be found in https://opensource.org/licenses/OSL-3.0
# or in the file LICENSE which is distributed along with the software.
Vorherrschende Sprache
Python
Sterne
2.7k
Forks
831
Ø Merge
3 T. 4 Std.
Gemergte PRs (30 T.)
7

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus aboutcode-org/scancode-toolkit

Alle Issues in aboutcode-org/scancode-toolkit

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

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