Skip to content

chore(license): switch from AGPL-3.0 to MIT - #47

Merged
IamCoder18 merged 1 commit into
mainfrom
chore/switch-to-mit-license
Aug 11, 2026
Merged

chore(license): switch from AGPL-3.0 to MIT#47
IamCoder18 merged 1 commit into
mainfrom
chore/switch-to-mit-license

Conversation

@IamCoder18

Copy link
Copy Markdown
Owner

Relicense under MIT for broader reuse and redistribution.

Changes

  • LICENSE — replaced AGPL-3.0 (661 lines) with the standard MIT license text (Copyright © 2026 Aarav Sharma)
  • packages/cli/package.jsonlicense: "AGPL-3.0-or-later""MIT"
  • README.md — License section: GNU Affero General Public License v3.0 or later → MIT

The npm license badge (shields.io/npm/l/@iamcoder18/huly-cli) reads the license field from package.json and will update automatically on next publish.

Notes for reviewers

  • This changes the project license from copyleft (AGPL) to permissive (MIT). Existing forks/remixes under prior versions remain under their original license — this only applies going forward.
  • Recommend a release as a minor bump (1.0.x → 1.1.0) since this is a meaningful license change downstream consumers should see.
  • The README's existing language around "self-hosted" / automation is unchanged; only the license identifier is affected.

Verification

head -1 LICENSE                                    # → MIT License
jq -r .license packages/cli/package.json           # → MIT
rg "AGPL" --type-not lock -g '!node_modules'       # → no matches

Relicense under MIT for broader reuse.

- Replace LICENSE with standard MIT text (© 2026 Aarav Sharma)
- packages/cli/package.json: license field MIT
- README.md: License section updated
@coderabbitai

coderabbitai Bot commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@IamCoder18, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 29 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 32464b09-44df-41e7-8c14-b20a0b6abc95

📥 Commits

Reviewing files that changed from the base of the PR and between f885870 and 0722664.

📒 Files selected for processing (3)
  • LICENSE
  • README.md
  • packages/cli/package.json

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@IamCoder18
IamCoder18 merged commit b40c66f into main Aug 11, 2026
3 checks passed
@kilo-code-bot

kilo-code-bot Bot commented Aug 11, 2026

Copy link
Copy Markdown

Code Review Summary

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 0
WARNING 0
SUGGESTION 1
Issue Details (click to expand)

SUGGESTION

File Line Issue
docs/development.md 139 Stale license statement — text still claims "This project follows the upstream Huly platform license," but the project is now independently MIT-licensed per this PR. The License section of docs/development.md should be updated to reference MIT and the new LICENSE file so contributors are not misled. The referenced "header at the top of src/cli.ts" also does not exist in the current source, so that sentence should be reworded or removed.
Files Reviewed (3 files)
  • LICENSE - 0 issues (canonical MIT text, copyright year 2026 and holder match PR author)
  • README.md - 0 issues (line 166 License section correctly switched to MIT)
  • packages/cli/package.json - 0 issues (SPDX identifier MIT is valid and matches LICENSE)

Fix these issues in Kilo Cloud


Reviewed by minimax-m3 · Input: 55.2K · Output: 8.4K · Cached: 191.3K

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant