CodeEditApp / CodeEditApp/CodeEditLanguages
License clarification: which license governs CodeEditLanguages?
- 主要言語
- Swift
- スター
- 133
- フォーク
- 55
- PR マージ指標
- 30日以内にマージされた PR はありません
説明
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!
コントリビューションガイド
このリポジトリのコントリビューションガイドは索引されていません
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- swift
- 領域
- documentation
- issue の種類
- ドキュメント
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 活発さ
- 静か
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 35/100