Add GNU General Public License v3 text

[dark-Invincible]

Added the full text of the GNU General Public License version 3.

Summary by CodeRabbit

• Documentation
  • Added complete GNU General Public License version 3 (GPLv3) documentation, including terms, conditions, and guidance for proper license application.

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

[coderabbitai]

Walkthrough

A GNU General Public License version 3 (GPLv3) license document is added to the repository. The file includes the complete legal text, terms, conditions, warranty disclaimers, liability limitations, and guidance for applying the license to programs.

Changes

Cohort / File(s)	Change Summary
License addition License.md	Adds complete GPLv3 license text including preamble, 17 sections of terms and conditions, definitions, permissions, conveyance rules, warranty disclaimers, liability limitations, and instructions for applying the license

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

This is purely a legal document addition with no executable code or logic. Review consists of confirming the GPLv3 text is complete and properly formatted.

Poem

🐰 A license arrives, so grand and free,
GPLv3 flows like a rabbit's decree,
Open and fair for all to share,
With terms and conditions laid bare,
Now code hops forth without a care! 🌱

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 accurately describes the main change: adding the GNU General Public License v3 text as a new file (License.md).
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

---

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.}

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

License.md (1)

10-10: Standardize markdown heading style across the document.

The document mixes heading styles (ATX with ## vs. expected setext style with underlines), creating linting failures. Additionally, line 542 uses emphasis _END OF TERMS AND CONDITIONS_ as a heading, which violates markdown conventions.

This is a repeated linting violation. Consider converting all ATX headings to setext style (underlines) to align with the markdown linter's configured standard. For example:

-## Preamble
+Preamble
+=========

Alternatively, if preserving the exact GPLv3 text is prioritized, configure the linter to accept ATX-style headings or disable the heading-style rule for this file.

Also applies to: 66-66, 68-68, 105-105, 142-142, 164-164, 178-178, 190-190, 219-219, 299-299, 353-353, 377-377, 387-387, 410-410, 471-471, 482-482, 491-491, 513-513, 523-523, 534-534, 544-544

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4579efc and 7209d4c.

📒 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 context for style improvements in formal legal documents.

LanguageTool has flagged multiple style suggestions (wordiness, phrase usage) across the document. However, since this is the official GPLv3 license text, modifying wording could:

• Alter the legal meaning or interpretation
• Create inconsistency with the official FSF version
• Complicate license compliance verification

If this document should be a verbatim copy of the official GPLv3, suppress style linting checks. If this is an adapted version, review each suggestion in context of legal accuracy.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Fix HTML-encoded angle brackets that break URL rendering.

Lines 5 and 588 use HTML entities (< and >) instead of literal angle brackets. This will cause URLs to render with visible entity codes instead of proper brackets:

&lt;<http://fsf.org/>&gt;  → displays as "&lt;<http://fsf.org/>&gt;" instead of "<http://fsf.org/>"

Replace the HTML entities with literal < and > characters:

-_Copyright © 2007 Free Software Foundation, Inc. &lt;<http://fsf.org/>&gt;_
+_Copyright © 2007 Free Software Foundation, Inc. <http://fsf.org/>_

-&lt;<http://www.gnu.org/licenses/>&gt;.
+<http://www.gnu.org/licenses/>.

Also applies to: 588-588

🤖 Prompt for AI Agents

In License.md around lines 5 and 588, HTML-encoded angle brackets (< and
>) are used around URLs which prevents proper rendering; replace those
entities with literal angle bracket characters (< and >) so the lines read with
actual <http://fsf.org/> style brackets (ensure you update both occurrences at
line 5 and line 588).