license folder

[rajapandi1234]

Summary by CodeRabbit

• Chores
  • Added license documentation files for Apache 2.0, Eclipse Public License 1.0, MIT, and Mozilla Public License 2.0.
  • Added copyright notices document listing attributions for included open-source components.

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

[coderabbitai]

Warning

Rate limit exceeded

@rajapandi1234 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 14 minutes and 17 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between f309c70 and 908b190.

📒 Files selected for processing (2)

• licenses/EPL-2.0.txt‎
• licenses/NOTICE

Walkthrough

Added five new license and attribution files to the repository: Apache-2.0, EPL-1.0, MIT, and MPL-2.0 license texts, plus a NOTICE document containing copyright notices for included open-source components.

Changes

Cohort / File(s)	Summary
License Texts licenses/Apache-2.0.txt, licenses/EPL-1.0.txt, licenses/MIT.txt, licenses/MPL-2.0.txt	Added standard open-source license texts with full terms, definitions, obligations, and boilerplate notices
Attribution licenses/NOTICE	Added copyright notice document enumerating open-source components (SLF4J, Jackson, JUnit 5, Maven Plugins, git-commit-id-plugin, MOSIP Kernel) with corresponding licenses and references

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Hop hop, the licenses now in place,
Apache, Eclipse, MIT with grace,
MPL and notices, all accounted for—
Our code rests safe on legal shore! 📜✨

Pre-merge checks

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'license folder' is vague and non-descriptive; it describes the directory location rather than the actual content or purpose of the changes.	Use a more descriptive title that explains what licensing changes are being added, such as 'Add Apache 2.0, EPL, MIT, and MPL 2.0 licenses' or 'Add license files and copyright notices'.

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

---

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

Fix all issues with AI Agents 🤖

In @licenses/NOTICE:
- Line 17: The NOTICE file references inconsistent license filenames (e.g.,
"LICENSE-MIT.txt", "LICENSE-APACHE-2.0.txt", "LICENSE-MPL-2.0.txt") that don't
match the actual files (MIT.txt, Apache-2.0.txt, MPL-2.0.txt); update the
strings in NOTICE (lines referencing "LICENSE-MIT.txt",
"LICENSE-APACHE-2.0.txt", "LICENSE-MPL-2.0.txt") to the actual filenames
(MIT.txt, Apache-2.0.txt, MPL-2.0.txt) or alternatively rename the actual files
to match the referenced names so all references are consistent.
- Line 68: The NOTICE references "LICENSE-LGPL-3.0.txt" but that file is
missing; either add the full LGPL-3.0 license file named LICENSE-LGPL-3.0.txt
into the licenses/ directory (copy the official LGPL-3.0 text) or remove the
reference from licenses/NOTICE and update imagedecoder/pom.xml
(git-commit-id-plugin related mention) if it expects that license; ensure the
NOTICE entry and the repository licensing metadata (licenses/NOTICE and
imagedecoder/pom.xml) are consistent after the change.
- Around line 34-42: The NOTICE references are inconsistent and some license
files are missing: add the correct Eclipse Public License 2.0 file as
LICENSE-EPL-2.0.txt (to match the JUnit 5 entry for
org.junit.vintage:junit-vintage-engine), add the LGPL-3.0 license as
LICENSE-LGPL-3.0.txt (to satisfy the git-commit-id-plugin entry), and then
reconcile naming between NOTICE and the licenses directory—either rename
existing files to the LICENSE-<ID>.txt pattern or update NOTICE entries (the
package identifiers like org.junit.vintage:junit-vintage-engine and
git-commit-id-plugin) so the referenced filenames exactly match the files
present.

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7736cb9 and f309c70.

📒 Files selected for processing (5)

• licenses/Apache-2.0.txt
• licenses/EPL-1.0.txt‎
• licenses/MIT.txt
• licenses/MPL-2.0.txt
• licenses/NOTICE

🧰 Additional context used

🪛 LanguageTool

licenses/MPL-2.0.txt

[style] ~48-~48: Consider removing “of” to be more concise
Context: ...tial grant or subsequently, any and all of the rights conveyed by this License. 1.10....

(ALL_OF_THE)

---

[style] ~107-~107: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...te The licenses granted in Section 2.1 with respect to any Contribution become effective for e...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

---

[style] ~212-~212: As an alternative to the over-used intensifier ‘absolutely’, consider replacing this phrase.
Context: ...lf of any Contributor. You must make it absolutely clear that any such warranty, support, indemn...

(EN_WEAK_ADJECTIVE)

---

[style] ~224-~224: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...y with any of the terms of this License with respect to some or all of the Covered Software due...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

---

[style] ~242-~242: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ...non-compliance by some reasonable means prior to 60 days after You have come back into c...

(EN_WORDINESS_PREMIUM_PRIOR_TO)

---

[style] ~247-~247: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ...h Contributor, and You become compliant prior to 30 days after Your receipt of the notic...

(EN_WORDINESS_PREMIUM_PRIOR_TO)

---

[style] ~254-~254: ‘any and all’ might be wordy. Consider a shorter alternative.
Context: ...tent, then the rights granted to You by any and all Contributors for the Covered Software u...

(EN_WORDINESS_PREMIUM_ANY_AND_ALL)

---

[style] ~259-~259: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ...or Your distributors under this License prior to termination shall survive termination. ...

(EN_WORDINESS_PREMIUM_PRIOR_TO)

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)

🔇 Additional comments (4)

licenses/MIT.txt (1)

1-9: Standard MIT License text approved.

This is an authentic, unmodified MIT license with appropriate copyright attribution for QOS.ch Sarl. The license text is complete and correctly formatted.

licenses/EPL-1.0.txt‎ (1)

1-86: Standard Eclipse Public License v1.0 text approved.

This is an authentic, unmodified EPL-1.0 license. All required sections (Definitions, Grant of Rights, Requirements, Commercial Distribution, Warranty, Liability, and General terms) are present and complete.

licenses/MPL-2.0.txt (1)

1-374: Standard Mozilla Public License v2.0 text approved.

This is an authentic, unmodified MPL-2.0 license. All required sections (Definitions, License Grants, Responsibilities, Termination, Warranties, Liability, Litigation, Miscellaneous, Versions, and Exhibits) are present and complete.

Note: Static analysis tools flag wordiness in legal language (e.g., "with respect to", "prior to", "any and all" at lines 107, 224, 242, 247, 254, 259). These are intentional terms in standardized legal documents and should not be modified.

licenses/Apache-2.0.txt (1)

1-200: License text looks good.

The Apache License 2.0 text is complete and accurate. No changes needed.