License clarification: which license governs CodeEditLanguages?

Open
#94 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
swift
Domain
documentation

Research direction

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.

Written by the indexing model from the issue text.

Description

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!

Dominant language
Swift
Stars
133
Forks
56
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CodeEditApp/CodeEditLanguages

All issues in CodeEditApp/CodeEditLanguages

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.