You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! We depend on CodeEditSymbols in a small macOS app and want to ship it
with correct attribution for the packages we bundle.
This repository doesn't currently have a LICENSE file, and there's no license
statement in the README — so there's no explicit grant covering redistribution
of the package inside a distributed application. The sibling repos in the org
(CodeEdit, CodeEditSourceEditor) are MIT, so we suspect that's the intended
license here too and the LICENSE file just hasn't been added yet.
Would the team be open to adding the org's standard MIT LICENSE? It would let
downstream apps like ours reproduce the required attribution correctly.
We're also contributing fixes upstream — see #22 — so we're invested in the
package's health.
Hi, I ship a paid macOS app built on CodeEditSourceEditor, which bundles CodeEditLanguages and CodeEditSymbols. Neither has a license file (see the open issues). Could you add the MIT license used by your other packages, or confirm in writing that these two packages may be redistributed under MIT? Thank you.
Activity
xdevaux commentedon Oct 30, 2026
Hi, I ship a paid macOS app built on CodeEditSourceEditor, which bundles CodeEditLanguages and CodeEditSymbols. Neither has a license file (see the open issues). Could you add the MIT license used by your other packages, or confirm in writing that these two packages may be redistributed under MIT? Thank you.