Skip to content

docs: align licence claims with the LICENSE file - #1

Open
cristianxruvalcaba-coder wants to merge 1 commit into
mainfrom
fix/licence-claims-2026-08-19
Open

docs: align licence claims with the LICENSE file#1
cristianxruvalcaba-coder wants to merge 1 commit into
mainfrom
fix/licence-claims-2026-08-19

Conversation

@cristianxruvalcaba-coder

Copy link
Copy Markdown
Contributor

The relicense to FSL-1.1-Apache on 2026-08-18 changed LICENSE but not the README or package metadata. This repo has since been publicly advertising a licence it does not carry.

What changed: every README licence claim now matches the LICENSE file, stated as FSL-1.1-Apache (converts to Apache 2.0 after two years) so neither half is misleading on its own. Where a package.json declared Apache-2.0, it now declares SEE LICENSE IN LICENSE, because FSL is not an SPDX identifier and npm warns on invalid expressions.

No licence is being changed here. This only makes the documentation agree with the grant that is already in force.

🤖 Generated with Claude Code

https://claude.ai/code/session_01SXZExtYaFJjKwrBuE1YTXK

The 2026-08-18 relicense to FSL-1.1-Apache updated LICENSE but not the
README or package metadata, leaving these repos publicly advertising a
licence they no longer carry.

FSL 1.1 is source-available with a competing-use restriction that converts
to Apache 2.0 two years after each release, so the wording states both
halves rather than either alone.

package.json uses "SEE LICENSE IN LICENSE" because FSL is not an SPDX
identifier and npm warns on invalid expressions.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SXZExtYaFJjKwrBuE1YTXK
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