feat: add license

[sosweetham]

Description of change

adds license

Issue Number

n/a

Type of change

• Update (a change which updates existing functionality)

How the change has been tested

n/a

Change checklist

n/a adds license

• I have ensured that the CI Checks pass locally
• I have removed any unnecessary logic
• My code is well documented
• I have signed my commits
• My code follows the pattern of the application
• I have self reviewed my code

Summary by CodeRabbit

• Documentation
  • Added a LICENSE file with the MIT License, clarifying permissions for use, modification, and redistribution of the software.
  • Improves transparency around legal terms for end users and contributors.
• Chores
  • Updated project assets to include licensing information at the repository root.
  • No changes to functionality, UI, or performance; the application behavior remains unchanged.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Added a new MIT License file at the repository root. No source code or public interfaces were changed.

Changes

Cohort / File(s)	Summary of Changes
Licensing `LICENSE`	Added MIT License text with copyright notice and standard terms.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I nibble the edges of legal leaves,
A LICENSE sprouts where code now breathes.
MIT winds in gentle prose,
Protects the patch where our repo grows.
Thump-thump—approved with careful sight,
Small change today, permissions bright.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/add-license

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4444dc9 and 5037d18.

📒 Files selected for processing (1)

• LICENSE (1 hunks)

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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