Skip to content

fix(readme): correct license badge and text from MIT to ELv2#2

Open
kh3rld wants to merge 2 commits into
mainfrom
fix/license-elv2-org-readme
Open

fix(readme): correct license badge and text from MIT to ELv2#2
kh3rld wants to merge 2 commits into
mainfrom
fix/license-elv2-org-readme

Conversation

@kh3rld

@kh3rld kh3rld commented Jun 11, 2026

Copy link
Copy Markdown
Member

Summary

The core library moved to Elastic License 2.0 at v4.8.0, but the org profile README still showed the MIT badge and stated "MIT licensed: safe for enterprise, commercial, and closed-source use" — which misrepresents ELv2's managed-service restriction.

Changes:

  • Badge: License-MIT-blue.svg -> License-Elastic--2.0-007ec6 (matches kreuzberg repo style)
  • "Why Choose Kreuzberg" bullet: corrected to ELv2 with the v4.7.x-and-below MIT note, tightened wording

Sweep results (all other core repos verified accurate)

Repo LICENSE README badge Status
kreuzberg ELv2 ELv2 correct
kreuzcrawl ELv2 ELv2 correct
kreuzberg-cloud BUSL-1.1 BUSL-1.1 correct
html-to-markdown MIT MIT correct (genuinely MIT)
tree-sitter-language-pack MIT MIT correct (genuinely MIT)
alef MIT MIT correct (genuinely MIT)
liter-llm MIT MIT correct (genuinely MIT)
.github org README -- was MIT fixed -> ELv2

Test plan

  • Confirm badge renders correctly on https://github.com/kreuzberg-dev
  • Confirm "Why Choose Kreuzberg" bullet accurately reflects ELv2 restrictions
  • Confirm kreuzberg/kreuzberg LICENSE file content is ELv2 (GitHub detects it as "Other" — known limitation, ELv2 is not in GitHub's Licensee database)

The core library moved to Elastic License 2.0 at v4.8.0.
Update the org profile badge and the "Why Choose Kreuzberg" bullet
to reflect ELv2, with a note that v4.7.x and below remain MIT.
@kh3rld kh3rld self-assigned this Jun 11, 2026
@kh3rld kh3rld added the documentation Improvements or additions to documentation label Jun 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant