Add GNU General Public License v3

[dark-Invincible]

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

Summary by CodeRabbit

• Chores
  • Added GNU General Public License version 3 to establish the project's licensing terms.

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

[coderabbitai]

Walkthrough

Added LICENSE.md file containing the complete GNU General Public License version 3 text, including the preamble, detailed terms and conditions (sections 0–17), supplementary terms, termination provisions, and instructions for applying the license to new programs.

Changes

Cohort / File(s)	Summary
License Addition LICENSE.md	Added full GNU General Public License v3 text with all sections, terms, conditions, and guidance for license application.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A license arrives with a flourish so grand,
GNU's words now protect all the work in this land,
Version three stands firm, a rabbit's delight,
Freedom and fairness, now written in 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 'Add GNU General Public License v3' directly and accurately describes the main change in the pull request, which is adding the LICENSE.md file containing the full GNU General Public License version 3 text.
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.}

[dark-Invincible]

@yogesh0509 I have raised PR Kindly check that

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

LICENSE.md (1)

10-10: Resolve markdown heading style inconsistencies.

The file uses ATX-style headings (###) throughout, but the project's markdown linting expects setext-style underlines. Additionally, Line 542 uses emphasis (_END OF TERMS AND CONDITIONS_) rather than a proper heading.

To align with markdown standards, consider converting headings to setext style or updating the linter configuration if ATX style is preferred.

Example conversion for setext style:

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

- ### 0. Definitions
+ 0. Definitions
+ ---------------

For Line 542, replace emphasis with a proper heading:

- _END OF TERMS AND CONDITIONS_
+ END OF TERMS AND CONDITIONS
+ ============================

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 e0c30f7 and 20bf8d6.

📒 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 (2)

LICENSE.md (2)

1-595: Approve: GPL v3 license text is complete and accurate.

The license document appears to be the official and complete GPL v3 text from the Free Software Foundation. Content-wise, it correctly includes all required sections (0–17), the preamble, termination provisions, and application guidance.

---

1-595: License addition appears compatible with existing dependencies.

Adding GPL v3 to this frontend project is appropriate. A spot-check of the dependency tree shows that primary dependencies (React, Next.js, ethers, viem, wagmi, Radix UI, and others) use MIT or Apache-2.0 licenses, which are permissive and compatible with GPL v3. No AGPL or conflicting copyleft licenses were detected.

Since this is the first license being formally added to the project with no prior licensing history, there are no existing license conflicts to resolve. Going forward, ensure that any new dependencies added maintain compatibility with GPL v3 (avoid GPL v2-only or AGPL licenses if the codebase will be distributed).