CodeEditApp / CodeEditApp/CodeEditLanguages

License clarification: which license governs CodeEditLanguages?

Aberta
#94 1 comentário 1 reação 0 responsáveis Ver no GitHub
Linguagem predominante
Swift
Estrelas
133
Forks
55
Métricas de merge de PRs
Nenhum PR com merge em 30d

Descrição

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!

Guia de contribuição

Nenhum guia de contribuição indexado para este repositório

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Avaliação

Stack de tecnologia
swift
Domínio
documentation
Tipo de issue
Documentação
Dificuldade
4/5
Tempo estimado
3-5 dias
Status de atividade
Pouca atividade
Clareza
Razoavelmente clara
Facilidade para iniciantes
35/100

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.