Would you consider adding a LICENSE file?

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.

Thanks so much!

Review the repository's current README and compare the licensing in the sibling CodeEdit and CodeEditSourceEditor repositories. Confirm that the org's standard MIT license applies here, then add the LICENSE file and a README license statement; done means downstream users can identify the redistribution and attribution terms.

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