chore(license): add GPL v3 license file

[LavKumarShakya]

We are Team NULL
Added a LICENSE.md file to clearly define usage and distribution rights for the project.

The project is now explicitly licensed under the GNU General Public License v3, which helps contributors and users understand their rights and obligations when using or modifying the code.

Summary by CodeRabbit

• Chores
  • Added GPL v3 license file defining the software usage and distribution terms.

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

[coderabbitai]

Walkthrough

A GNU General Public License Version 3 file is added to the repository. The LICENSE.md contains the complete GPLv3 text, including definitions, permissions, distribution terms, termination rules, patent provisions, and instructions for applying the license to new programs.

Changes

Cohort / File(s)	Summary
License file LICENSE.md	Added complete GNU General Public License Version 3 text with preamble, terms, usage instructions, and guidance for applying the license to software

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Verify that the GPLv3 license text is complete and unmodified
• Confirm the file format and encoding are correct

Poem

🐰 A license so grand, a shield for the code,
GPL's words light the open-source road,
Freedom and fairness now codified bright,
The rabbit approves—this feels oh-so-right! 🎉

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 clearly describes the main change: adding a GPL v3 license file to the repository.
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 baaf8cf and 737c7e1.

📒 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] ~290-~290: 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 ...

(GENERAL_XX)

---

[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. Moreover,...

(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 License...

(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] ~663-~663: 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

661-661: Spaces inside code span elements

(MD038, no-space-in-code)

🔇 Additional comments (1)

LICENSE.md (1)

1-668: Excellent: official GPLv3 license added.

The file contains the complete, official GNU General Public License v3 text (dated 29 June 2007). This clearly defines the project's licensing terms, usage rights, and obligations for contributors and users.

Note: Static analysis flagged style suggestions (wordiness, phrasing), but these are inappropriate for a legal document. License text should remain unchanged from the official version to avoid legal ambiguity.

---

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