Add LICENSE.md

[singhshaurya01]

Added LICENSE.md as requested in Stability Nexus guidelines:

This is one of the tasks sanctioned by StabilityNexus.

Summary by CodeRabbit

• Chores
  • Added license file to the project.

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

[github-actions]

⚠️ No issue was linked in the PR description.
Please make sure to link an issue (e.g., 'Fixes #issue_number')

[coderabbitai]

Walkthrough

A LICENSE.md file is added containing the complete GNU General Public License version 3 text, including definitions, terms, conditions, and instructions for applying the license to distributed works. No code or API changes are introduced.

Changes

Cohort / File(s)	Summary
License Addition LICENSE.md	Adds GPLv3 license text with preamble, definitions, sections 0–17 covering permissions, conditions, and restrictions for source and object code distribution

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Straightforward file addition; review should verify license text accuracy and completeness

Poem

🐰 A license arrives, GPLv3 so grand,
The code runs free across the land,
With open arms and open source,
We hop along our rightful course! 🌱

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 LICENSE.md' directly and clearly describes the main change in the pull request—adding a LICENSE.md file.
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 d07d817 and dc16251.

📒 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: LGTM! Adding LICENSE.md is appropriate.

The PR successfully adds the complete GNU General Public License v3 text to the repository, fulfilling the stated objective to satisfy Stability Nexus guidelines. The license content is accurate and comprehensive.

A note on static analysis findings: markdownlint flagged heading style inconsistencies (preferring setext-style underlines over ATX-style # headings) and one emphasis-based separator line instead of a heading. These are minor formatting preferences and don't affect the legal validity or clarity of the license text. The current formatting (ATX headings) is common and readable. Similarly, LanguageTool's style suggestions about wording should not be applied to a license file, as the exact text of GPLv3 carries legal significance and should remain unchanged.

---

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

[github-actions]

⚠️ No issue was linked in the PR description.
Please make sure to link an issue (e.g., 'Fixes #issue_number')