CodeEditApp / CodeEditApp/CodeEditLanguages

License clarification: which license governs CodeEditLanguages?

Abierto
#94 1 comentario 1 reacción 0 asignados Ver en GitHub
Lenguaje dominante
Swift
Estrellas
133
Forks
55
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

Hi, and thanks for maintaining CodeEditLanguages — bundling the tree-sitter grammars into a single precompiled xcframework is a genuinely clean way to consume tree-sitter on macOS.

I'd like to depend on this package in a commercial macOS app and want to attribute it correctly, but I can't determine the license for **this specific package**: there's no `LICENSE` file in the repo root, and GitHub's license API returns nothing for it. The main CodeEdit app is MIT, but `CodeEditLanguages` doesn't appear to carry its own license file.

Could you help clarify:

1. **What license governs `CodeEditLanguages` itself?** Is it intended to be MIT, consistent with the rest of the CodeEdit org? If so, would you consider adding a `LICENSE` file to the repo root so it's unambiguous and detectable by tooling (GitHub, SPM, license scanners)?

2. **Attribution for the bundled grammars** — each upstream tree-sitter grammar carries its own license (MIT/Apache-2.0/etc.). Is there an aggregate `NOTICE`/attribution you'd recommend bundling, or should consumers attribute each grammar from its upstream repo?

Happy to open a PR adding a `LICENSE` file (and a grammar `NOTICE`, if useful) if that would save you time. Thanks again!

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Línea de trabajo

Start by checking the repository root for the missing LICENSE file and reviewing how the bundled tree-sitter grammars and their upstream licenses are identified. Confirm the package’s governing license and the needed grammar attribution with maintainers; done means the repository contains the agreed LICENSE and, if needed, a NOTICE or documented attribution guidance.

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

Evaluación

Stack tecnológico
swift
Área
documentation
Tipo de issue
Documentación
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Tranquilo
Claridad
Bastante claro
Aptitud para principiantes
35/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.