license folder

[rajapandi1234]

Summary by CodeRabbit

• Documentation
  • Added comprehensive open-source license files including AGPL, Apache 2.0, BSD, EPL, MIT, MPL, LGPL, and JSON licenses.
  • Added third-party component notices and license attributions.

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

[coderabbitai]

Walkthrough

This PR introduces a comprehensive licensing infrastructure by adding ten license text files (AGPL-3.0, Apache 2.0, BSD variants, EPL variants, MIT, MPL 2.0, JSON) and a compliance notice document that aggregates third-party component licenses and copyright information.

Changes

Cohort / File(s)	Summary
License Texts licenses/AGPL-3.0-only.txt, licenses/Apache-2.0.txt, licenses/BSD-2.0.txt, licenses/BSD-3-Clause.txt, licenses/EPL-1.0.txt, licenses/EPL-2.0.txt, licenses/JSON.txt, licenses/LGPL-3.0-only.txt, licenses/MIT.txt, licenses/MPL-2.0.txt	Added ten open-source and proprietary license text files containing complete license terms, conditions, grants, disclaimers, and attribution requirements for compliance reference.
Compliance Documentation licenses/NOTICE	Added consolidated third-party notice document enumerating components by license type (Apache 2.0, MIT, EPL, LGPL, AGPL-3.0, MPL-2.0, BSD, CDDL/GPL, JSON) with copyright notices, compliance obligations, and references to full license texts.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 A warren of licenses, organized with care,
Compliance and permissions woven everywhere,
MIT, Apache, EPL in harmonious rows,
Legal foundations that responsibly grow! ✨📜

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'license folder' is vague and does not clearly convey what was changed. While the PR does add license files, the title lacks specificity about the actual changes and appears generic.	Use a more descriptive title such as 'Add open source license files' or 'Add license documentation (Apache, MIT, BSD, AGPL, EPL, LGPL, MPL, JSON)' to clearly indicate the purpose and scope of the changes.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
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: 3

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d009a5b and b9e927f.

📒 Files selected for processing (11)

• licenses/AGPL-3.0-only.txt‎
• licenses/Apache-2.0.txt
• licenses/BSD-2.0.txt
• licenses/BSD-3-Clause.txt‎
• licenses/EPL-1.0.txt
• licenses/EPL-2.0.txt
• licenses/JSON.txt‎
• licenses/LGPL-3.0-only.txt
• licenses/MIT.txt‎
• licenses/MPL-2.0.txt‎
• licenses/NOTICE

🧰 Additional context used

🪛 LanguageTool

licenses/LGPL-3.0-only.txt

[style] ~69-~69: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ished by the Free Software Foundation. If the Library as you received it specifie...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

---

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

(GENERAL_XX)

---

[style] ~145-~145: ‘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] ~176-~176: 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] ~210-~210: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...survive such relicensing or conveying. If you add terms to a covered work in acco...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

---

[style] ~218-~218: ‘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] ~220-~220: ‘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] ~225-~225: 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] ~225-~225: 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] ~237-~237: 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] ~247-~247: 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] ~247-~247: ‘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] ~252-~252: ‘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] ~261-~261: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ished by the Free Software Foundation. If the Program specifies that a proxy can ...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

---

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

licenses/EPL-2.0.txt

[style] ~22-~22: Consider a more concise word here.
Context: ...iles of the Program solely in each case in order to link to, bind by name, or subclass the ...

(IN_ORDER_TO_PREMIUM)

---

[grammar] ~33-~33: Use a hyphen to join words.
Context: ... needed, if any. For example, if a third party patent license is required to allo...

(QB_NEW_EN_HYPHEN)

---

[style] ~39-~39: Consider replacing this phrase with the adverb “reasonably” to avoid wordiness.
Context: ...and informs Recipients how to obtain it in a reasonable manner on or through a medium customarily used...

(IN_A_X_MANNER)

---

[style] ~40-~40: Did you mean ‘different from’? ‘Different than’ is often considered colloquial style.
Context: ...e the Program under a license different than this Agreement, provided that such lice...

(DIFFERENT_THAN)

---

[style] ~52-~52: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...are may accept certain responsibilities with respect to end users, business partners and the li...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

---

[style] ~52-~52: Consider a more concise word here.
Context: ...ged intellectual property infringement. In order to qualify, an Indemnified Contributor mus...

(IN_ORDER_TO_PREMIUM)

---

[style] ~69-~69: Consider a more concise word here.
Context: ...istribute copies of this Agreement, but in order to avoid inconsistency the Agreement is co...

(IN_ORDER_TO_PREMIUM)

licenses/Apache-2.0.txt

[style] ~161-~161: ‘any and all’ might be wordy. Consider a shorter alternative.
Context: ...ge, computer failure or malfunction, or any and all other commercial damages or losse...

(EN_WORDINESS_PREMIUM_ANY_AND_ALL)

licenses/EPL-1.0.txt

[style] ~16-~16: ‘in conjunction with’ might be wordy. Consider a shorter alternative.
Context: ...eparate modules of software distributed in conjunction with the Program under their own license agr...

(EN_WORDINESS_PREMIUM_IN_CONJUNCTION_WITH)

---

[grammar] ~32-~32: Use a hyphen to join words.
Context: ... needed, if any. For example, if a third party patent license is required to allo...

(QB_NEW_EN_HYPHEN)

---

[style] ~50-~50: Consider replacing this phrase with the adverb “reasonably” to avoid wordiness.
Context: ... and informs licensees how to obtain it in a reasonable manner on or through a medium customarily used...

(IN_A_X_MANNER)

---

[style] ~64-~64: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...are may accept certain responsibilities with respect to end users, business partners and the li...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

---

[style] ~64-~64: Consider a more concise word here.
Context: ...ged intellectual property infringement. In order to qualify, an Indemnified Contributor mus...

(IN_ORDER_TO_PREMIUM)

---

[style] ~84-~84: Consider a more concise word here.
Context: ...istribute copies of this Agreement, but in order to avoid inconsistency the Agreement is co...

(IN_ORDER_TO_PREMIUM)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: print / build-dockers

🔇 Additional comments (9)

licenses/JSON.txt‎ (1)

1-11: LGTM!

The JSON License text is complete and matches the official license from JSON.org.

licenses/Apache-2.0.txt (1)

1-200: LGTM!

The Apache License 2.0 text is complete and matches the official version. The static analysis style hint about "any and all" is a false positive—this is standard legal language that should remain unchanged.

licenses/AGPL-3.0-only.txt‎ (1)

1-235: LGTM!

The GNU Affero General Public License v3 text is complete and matches the official FSF version.

licenses/MPL-2.0.txt‎ (1)

1-151: LGTM!

The Mozilla Public License 2.0 text is complete and matches the official version, including both Exhibit A and Exhibit B.

licenses/EPL-1.0.txt (1)

1-86: LGTM!

The Eclipse Public License 1.0 text is complete and matches the official version. The static analysis style hints are false positives—these are standard legal phrases that should remain unchanged in license documents.

licenses/NOTICE (4)

348-350: Verify external file reference or clarify if this is aspirational.

Line 349 references a THIRD-PARTY-NOTICES.txt file that is not present in this PR. Either this file should be added, or the reference should be updated if this file is not planned.

---

275-279: Clarify which license applies to H2 Database.

H2 Database is listed under the MPL-2.0 section but the description (lines 275–279) indicates it is dual-licensed under MPL 2.0 OR EPL 1.0. Please clarify which license this project has chosen to use, or add a note explaining the selection.

---

228-230: Excellent critical compliance warnings.

The document properly flags AGPL-3.0 implications for iText components and includes clear, actionable compliance notes. This is important for teams integrating or distributing this software.

Also applies to: 352-357

---

1-359: Well-structured compliance document.

The NOTICE file is comprehensive and well-organized by license category. Copyright notices, project names, and license information are consistently formatted. The document serves its purpose as a reference guide for third-party licensing obligations.