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

Abierto
  • ¿Algo no está bien?
#5,347 3 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 3 días

@Anurag-S1ngh ya está trabajando en esto.

Desde el 31/10/2026.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
search

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
Python
Estrellas
2.7k
Forks
831
Merge medio
3 d 4 h
PR fusionados (30 d)
7

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de aboutcode-org/scancode-toolkit

Todos los issues de aboutcode-org/scancode-toolkit

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.