Add GNU General Public License v3

[dark-Invincible]

Added the GNU General Public License version 3 to the project.

Summary by CodeRabbit

Documentation

• Added GPL-3 license documentation specifying legal terms, distribution requirements, modifications, warranty disclaimers, and liability limitations.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

A GNU General Public License version 3 (GPL-3) file has been added to the repository. The file contains the complete legal text including preamble, terms and conditions, definitions, permissions, conveying requirements, and guidance on applying the license to new programs.

Changes

Cohort / File(s)	Summary
License Documentation License.md	Added complete GPL-3 license text with preamble, 17 sections covering terms and conditions, definitions, source code, permissions, modification rights, distribution requirements, patent provisions, warranty disclaimers, liability limitations, and guidance for applying license to new programs

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Verify the GPL-3 license text matches the official version
• Confirm file is placed appropriately in the repository root

Poem

A license unfurled, so noble and free,
GPL-3 spreads beneath every tree! 🌳
Rights protected, code shared wide,
With open-source joy as our guide,
Now users can trust, and developers glide. 🐰✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Add GNU General Public License v3' directly and accurately describes the main change: adding a complete GPL-3 license file (License.md) to the project.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 41a8bf0 and 85ca7d1.

📒 Files selected for processing (1)

• License.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

License.md

[style] ~19-~19: To make your writing flow more naturally, try moving ‘also’ before the verb.
Context: ...ic License for most of our software; it applies also to any other work released this way by ...

(ALSO_PLACEMENT)

---

[style] ~173-~173: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...by exercising rights under this License with respect to the covered work, and you disclaim any ...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

---

[style] ~253-~253: Consider using only “public” to avoid wordiness.
Context: ...ce of the work are being offered to the general public at no charge under subsection 6d. A se...

(GENERAL_XX)

---

[style] ~363-~363: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ... the violation by some reasonable means prior to 60 days after the cessation. Moreover,...

(EN_WORDINESS_PREMIUM_PRIOR_TO)

---

[style] ~369-~369: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ...ight holder, and you cure the violation prior to 30 days after your receipt of the notic...

(EN_WORDINESS_PREMIUM_PRIOR_TO)

---

[style] ~379-~379: Consider a more concise word here.
Context: ...are not required to accept this License in order to receive or run a copy of the Program. A...

(IN_ORDER_TO_PREMIUM)

---

[style] ~380-~380: To make your writing clearer, consider a shorter, more direct phrase.
Context: ...tion of a covered work occurring solely as a consequence of using peer-to-peer transmission to rece...

(AS_A_CONSEQUENCE_OF)

---

[style] ~420-~420: To make your writing clearer, consider a shorter, more direct phrase.
Context: ...ude claims that would be infringed only as a consequence of further modification of the contributor...

(AS_A_CONSEQUENCE_OF)

---

[uncategorized] ~460-~460: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...conveying the work, and under which the third party grants, to any of the parties who would...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[style] ~465-~465: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ...nt, or that patent license was granted, prior to 28 March 2007. Nothing in this License...

(EN_WORDINESS_PREMIUM_PRIOR_TO)

---

[style] ~475-~475: ‘So as to’ expresses purpose and is used in formal texts. Consider using “to”.
Context: ...se. If you cannot convey a covered work so as to satisfy simultaneously your obligations...

(SO_AS_TO)

---

[style] ~583-~583: This phrase is redundant (‘I’ stands for ‘interface’). Use simply “GUI”.
Context: ...am's commands might be different; for a GUI interface, you would use an “about box”. You sho...

(ACRONYM_TAUTOLOGY)

🪛 markdownlint-cli2 (0.18.1)

License.md

10-10: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)

---

66-66: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)

---

68-68: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)

---

105-105: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)

---

142-142: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)

---

164-164: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)

---

178-178: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)

---

190-190: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)

---

219-219: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)

---

299-299: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)

---

353-353: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)

---

377-377: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)

---

387-387: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)

---

410-410: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)

---

471-471: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)

---

482-482: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)

---

491-491: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)

---

513-513: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)

---

523-523: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)

---

534-534: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)

---

542-542: Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

544-544: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)

🔇 Additional comments (1)

License.md (1)

1-595: Consider the GPL-3 fidelity vs. project markdown standards trade-off.

This file adds the official GNU General Public License v3, which is legally significant. The static analysis hints include ~24 markdownlint warnings (mostly heading style inconsistencies between atx ## and setext style) and ~12 LanguageTool style suggestions (about wordiness in legal language).

Key considerations:

• Legal documents are typically best left unmodified from their official source to avoid introducing ambiguity or divergence from the canonical version.
• The markdownlint warnings are formatting preferences; the actual license text and meaning are unaffected.
• The LanguageTool suggestions (e.g., "prior to" → "before", "as a consequence of" → "due to") apply to legal language that is intentionally formal and should remain unchanged.

Recommendation: Verify this is the official GPL-3 v3 text from the Free Software Foundation and decide whether project markdown formatting consistency is worth the risk of modifying a legal document. If exact verbatim preservation is the priority, you may want to suppress the linting rules for this file or accept the warnings as acceptable for legal documentation.

Do you want me to verify that this is the official GPL-3 v3 text from FSF, and would you prefer to keep the text verbatim or align it with project markdown standards (which would involve reformatting headings)?

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}