license folder

[rajapandi1234]

Summary by CodeRabbit

• Chores
  • Added comprehensive license documentation for multiple open-source licenses used by the project, including AGPL 3.0, Apache License 2.0, BSD 2-Clause, CDDL 1.1, Eclipse Public License 1.0, LGPL 3.0, MIT, Mozilla Public License 2.0, and JSON License.
  • Added a notice file providing consolidated copyright and attribution information for third-party components.

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

[coderabbitai]

Walkthrough

Nine open-source license text files (AGPL-3.0, Apache-2.0, BSD-2-Clause, CDDL-1.1, EPL-1.0, JSON, LGPL-3.0, MIT, MPL-2.0) and a consolidated NOTICE file documenting third-party copyright attributions are added to the licenses directory for compliance documentation.

Changes

Cohort / File(s)	Summary
Open Source Licenses licenses/AGPL-3.0-only.txt, licenses/Apache-2.0.txt, licenses/BSD-2-Clause.txt, licenses/CDDL-1.1.txt, licenses/EPL-1.0.txt, licenses/JSON.txt, licenses/LGPL-3.0-only.txt, licenses/MIT.txt, licenses/MPL-2.0.txt	New license text files added containing complete legal terms for nine different open-source licenses including definitions, grant clauses, distribution obligations, warranty disclaimers, and additional provisions specific to each license.
Attribution & Notices licenses/NOTICE	New file consolidating copyright notices and license references for third-party components used by the project, with structured attribution information and references to individual project homepages.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 Ten licenses bound with care,
Legal text beyond compare!
Compliance documented well,
Open-source credentials tell.
A hoppy hop through licensing!

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 describe the primary changes, which involve adding multiple license files to the licenses directory.	Use a more descriptive title such as 'Add license files (AGPL, Apache, BSD, CDDL, EPL, JSON, LGPL, MIT, MPL)' or 'Add open-source license documentation' to clearly communicate the changeset purpose.

✅ 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: 1

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 76bbd1f and ef7ffc6.

📒 Files selected for processing (10)

• licenses/AGPL-3.0-only.txt‎
• licenses/Apache-2.0.txt
• licenses/BSD-2-Clause.txt
• licenses/CDDL-1.1.txt‎
• licenses/EPL-1.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/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)

⏰ 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). (2)

• GitHub Check: build-maven-apitest-commons / maven-build
• GitHub Check: Analyze (java-kotlin)

🔇 Additional comments (10)

licenses/EPL-1.0.txt‎ (1)

1-73: LGTM!

Standard Eclipse Public License v1.0 text. Appropriate for documenting EPL-licensed dependencies like JUnit 4.

licenses/MIT.txt (1)

1-12: LGTM!

Consolidated MIT License text covering multiple dependencies (Lombok, SLF4J, Auth0, BouncyCastle). Copyright notices align with the NOTICE file.

licenses/JSON.txt‎ (1)

1-11: Standard JSON License text with known compliance consideration.

This is the correct license text for org.json. Note that line 9 contains the clause "The Software shall be used for Good, not Evil," which some organizations flag as problematic due to its ambiguity. If your organization has concerns about this license, you may need to find alternative JSON libraries.

licenses/Apache-2.0.txt (1)

1-201: LGTM!

Standard Apache License 2.0 text. This covers the majority of third-party dependencies listed in the NOTICE file (Jackson, Spring, Hibernate Validator, and many others).

Note: The static analysis hint about wordiness on line 161 should be ignored—this is official license text and must not be modified.

licenses/BSD-2-Clause.txt (1)

1-9: LGTM!

Standard BSD 2-Clause License text for PostgreSQL JDBC Driver. Copyright notice matches the NOTICE file entry.

licenses/MPL-2.0.txt‎ (1)

1-374: LGTM!

Standard Mozilla Public License 2.0 text with complete definitions, terms, and exhibits. Appropriate for MOSIP Kernel Libraries and H2 Database.

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

1-236: Standard AGPL 3.0 text for iText libraries.

The license text is the standard GNU Affero General Public License v3.0, appropriate for documenting iText 5 and iText HTML2PDF dependencies. After correcting the version line issue above, this will be complete.

licenses/NOTICE (1)

1-190: Verify which additional license files are actually needed in this PR.

The NOTICE file references several licenses that don't have corresponding text files: GPL-2.0 with Classpath Exception (JavaMail, line 90), Eclipse Distribution License 1.0 (JAXB API, line 52), BSD 3-Clause (ExtentReports, Hamcrest), EPL 2.0 (JaCoCo, line 174), and LGPL 2.1 (Hibernate Core, line 60). Confirm whether these additional license text files are required for compliance in this PR.

licenses/LGPL-3.0-only.txt (1)

1-303: ✓ License text addition is appropriate; disregard style analysis hints.

The static analysis tool flagged 16 style/grammar suggestions (repetitive sentence beginnings, wordiness, etc.). These warnings do not apply to standard open-source license texts. License documentation must remain verbatim to the official versions—any stylistic edits introduce legal ambiguity and violate the integrity of the licensing terms. The file correctly includes both the LGPL-3.0-only preamble and the incorporated GPL-3.0 full text.

licenses/CDDL-1.1.txt‎ (1)

1-123: ✓ CDDL-1.1 license text is complete and properly structured.

The file includes all required sections: definitions, license grants, distribution obligations, version management, disclaimers, U.S. government clauses, miscellaneous provisions, responsibility clauses, and jurisdiction notices. The text aligns with the official CDDL-1.1 standard.