Add LICENSE.md to explain usage rights under GNU GPL v3

[sunilkumawat-96]

Problem: Contributors don’t know usage rights.

Solution: Add a LICENSE.md file.

License used: GNU General Public License v3 (GPLv3).

Result: Contributors can clearly see rules for using, modifying, and sharing the code.

Summary by CodeRabbit

Release Notes

• Documentation
  • Added GNU General Public License v3.0, clarifying project usage rights and distribution requirements for all users.

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

[coderabbitai]

Walkthrough

The GNU General Public License version 3.0 document has been added to LICENSE.md, containing the full legal text including preamble, terms, conditions, and compliance guidance. No code changes were made.

Changes

Cohort / File(s)	Summary
License Documentation LICENSE.md	Added complete GPL v3.0 license text with preamble, terms and conditions (sections 0–17), definitions, permissions, requirements for distribution, patent terms, and compliance notices

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Verification that the license text is the authentic GPL v3.0 document (consider comparing against official source)
• Confirmation that the license aligns with project intentions

Poem

A rabbit hops through legal prose,
Where freedoms flow and right it grows,
GPL's shield now shines so bright,
Protecting code with open might! 🐰📜✨

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 a LICENSE.md file to clarify usage rights under GNU GPL v3, which matches the changeset and PR objectives.
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: 0

🧹 Nitpick comments (1)

LICENSE.md (1)

1-6: Rename LICENSE.md to LICENSE per industry convention.

The file should be named LICENSE without the .md extension. GitHub, package managers, and most tools recognize the bare LICENSE filename for license discovery and display, while .md extensions may not be automatically recognized. This does not affect the legal status of the license but improves visibility and tooling support.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between baaf8cf and 76936ab.

📒 Files selected for processing (1)

• LICENSE.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

LICENSE.md

[style] ~18-~18: 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] ~23-~23: Consider using only “Public” to avoid wordiness.
Context: ...e referring to freedom, not price. Our General Public Licenses are designed to make sure that...

(GENERAL_XX)

---

[style] ~189-~189: ‘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] ~419-~419: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ... the violation by some reasonable means prior to 60 days after the cessation. Moreove...

(EN_WORDINESS_PREMIUM_PRIOR_TO)

---

[style] ~426-~426: ‘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] ~437-~437: 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. ...

(IN_ORDER_TO_PREMIUM)

---

[style] ~439-~439: 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)

---

[uncategorized] ~528-~528: 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] ~534-~534: ‘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 Licen...

(EN_WORDINESS_PREMIUM_PRIOR_TO)

---

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

(SO_AS_TO)

---

[style] ~662-~662: 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 s...

(ACRONYM_TAUTOLOGY)

🪛 markdownlint-cli2 (0.18.1)

LICENSE.md

660-660: Spaces inside code span elements

(MD038, no-space-in-code)

🔇 Additional comments (1)

LICENSE.md (1)

1-674: Do not apply style/wordiness refactors to the official GPLv3 text.

The static analysis tools flagged several instances of wordiness in sections 18, 23, 189, 419, 426, 437, 439, 528, 534, 545, and 662. While those are valid writing suggestions in general, the license text is the official GPLv3 v3.0 from the Free Software Foundation (dated June 29, 2007), and its exact wording is legally significant for compliance. Modifying the official license text—even for style improvements—could create ambiguity or compliance issues.

The license content itself is appropriate and complete for the repository. The license grants are clear, obligations are well-defined, and the guidance on applying the license to new programs is included.

To confirm this matches the official FSF GPLv3 v3.0, you may verify against the authoritative source at https://www.gnu.org/licenses/gpl-3.0.txt.