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

Ouverte
  • Quelque chose ne va pas ?
#5,347 4 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 3 jours

@Anurag-S1ngh y travaille déjà.

Depuis le 31/10/2026.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
45/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
python
Domaine
search

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.
Langage dominant
Python
Étoiles
2.7k
Forks
831
Merge moyen
2 j 19 h
PR mergées (30 j)
8

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de aboutcode-org/scancode-toolkit

Toutes les issues de aboutcode-org/scancode-toolkit

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.