Create NOTICE

[rajapandi1234]

Summary by CodeRabbit

• Documentation
  • Added a NOTICE file documenting all third-party licenses used by the project, including Apache License 2.0, MPL 2.0, MIT License, and others. Full license texts are available in the license/ directory.

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

[coderabbitai]

Walkthrough

A new NOTICE file is added to document third-party libraries and their associated licenses. The file references license texts available in the license/ directory and enumerates components from Spring, MOSIP, Jackson, JUnit, Bouncy Castle, and other dependencies with their respective license designations.

Changes

Cohort / File(s)	Summary
Compliance & Attribution NOTICE	New file detailing third-party library licenses (Apache 2.0, MIT, MPL 2.0, etc.) with reference to full license texts in license/ directory

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 A notice, so proper and fair,
Of licenses listed with care,
From Spring to Bouncy, each name in a row,
Compliance shines bright in the glow!
Hopping through legalities, nothing to fear, ✨

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 pull request title 'Create NOTICE' directly matches the main change: adding a new NOTICE file documenting third-party licenses.
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: 0

🧹 Nitpick comments (2)

NOTICE (2)

1-35: Add guidance on completeness and maintenance.

The NOTICE file provides good documentation of third-party libraries and their licenses. However, consider adding a note clarifying:

1. Completeness: Is this list exhaustive (all direct + transitive dependencies), or does it cover only direct runtime dependencies?
2. Maintenance: How should developers update this file when adding/upgrading dependencies? (e.g., "This file should be reviewed and updated whenever dependencies in pom.xml change.")
3. License directory: Confirm that the referenced license/ directory exists and is populated with the full license texts for all listed components.

🔎 Suggested addition (optional header/footer notes)

  The full text of each license is available in the `license/` directory.
+
+Note: This file documents direct and significant transitive dependencies.
+When updating dependencies, please review and update this NOTICE file accordingly.

---

17-17: Standardize dual/multi-license notation for consistency.

The file uses inconsistent notation for dual or mixed licenses:

• Line 17 (JUnit): 1.0 / 2.0 (version variants)
• Line 23 (H2): 2.0 / 1.0 (license variants with /)
• Line 31 (Javassist): (mixed) label

Consider standardizing the format. For example, use consistent separators and parenthetical notes:

-JUnit & JUnit Vintage — Eclipse Public License 1.0 / 2.0
+JUnit & JUnit Vintage — Eclipse Public License 1.0, 2.0

This improves clarity and makes the file easier to parse programmatically if needed.

Also applies to: 23-23, 31-31

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between db7e1c5 and 53ea348.

📒 Files selected for processing (1)

• NOTICE

⏰ 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: build-kernel / maven-build

🔇 Additional comments (1)

NOTICE (1)

7-33: LGTM — Good coverage and attribution.

The library list appears comprehensive and license attributions are accurate for commonly-used OSS components. The file follows standard NOTICE conventions and will help maintain legal compliance and transparency.