Repository navigation
Conversation
The owner changed the licence from MIT to AGPL-3.0-only on 2026-10-19: a ranger that has been hardened, logged or narrowed should not become a closed product on somebody else's bench, while a commercial exception stays available on request. LICENSE is now the verbatim AGPL-3.0 text, and Cargo.toml says license = "AGPL-3.0-only", so a crate built from this tree cannot claim otherwise. The rest of the change is the paperwork that makes the claim true rather than merely stated. - README closes with "Security & license": the copyleft, the commercial exception, the security policy, and the deep dive, in that order. - CONTRIBUTING.md is new and carries the CLA that keeps relicensing possible. Without a grant in every contribution, there would be nobody to sell the exception to. - THIRD-PARTY-NOTICES.md is new and generated from Cargo.lock rather than typed: 561 crates with the licence each keeps, 544 of them in the default build and 17 reached only by the tests, the fonts embedded in the binary, and the three crates where a copyleft option exists and a permissive arm is taken. MPL-2.0 option-ext is named as the one file-level copyleft in the tree. - RELEASES.md and release.yml put the notices in every archive, and the release notes now carry the written offer that section 6 of the licence asks for. - PLAN.md and PLAN-0.1.7.md keep their MIT reasoning as the record, with a dated note that the conclusion is superseded. AGENTS.md section 8 says in words that it governs dependencies, not this repository's own licence. A push to dev triggers no workflow, and none was dispatched. cargo xtask ci was green on this tree before the commit: fmt, no-network, language, packs, coverage, signature, no-content-engine, clippy -D warnings, and 470 tests.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The owner changed the licence from MIT to AGPL-3.0-only on 2026-10-19: a ranger that has been hardened, logged or narrowed should not become a closed product on somebody else's bench, while a commercial exception stays available on request.
LICENSE is now the verbatim AGPL-3.0 text, and Cargo.toml says license = "AGPL-3.0-only", so a crate built from this tree cannot claim otherwise. The rest of the change is the paperwork that makes the claim true rather than merely stated.
A push to dev triggers no workflow, and none was dispatched. cargo xtask ci was green on this tree before the commit: fmt, no-network, language, packs, coverage, signature, no-content-engine, clippy -D warnings, and 470 tests.