chore: add Apache 2.0 LICENSE file

[omwanere]

What does this PR do?

Adds an Apache 2.0 LICENSE file to the repository so GitHub can
properly detect the project's license.

Why?

The repository currently has no LICENSE file, which can cause
legal ambiguity for users and contributors.

Checklist

• License text taken from apache.org
• Matches other Supabase repositories

Summary by CodeRabbit

• Chores
  • Project is now licensed under the Apache License 2.0, including terms for copyright, patent grants, redistribution, and liability limitations.

[coderabbitai]

📝 Walkthrough

Walkthrough

A new Apache License 2.0 file has been added to the repository. The license file includes the complete standard text with copyright grants, patent terms, redistribution conditions, warranty disclaimers, and liability limitations.

Changes

Cohort / File(s)	Summary
License LICENSE	Added Apache License, Version 2.0 with complete standard terms including copyright grant, patent license, and legal disclaimers.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore: add Apache 2.0 LICENSE file' accurately describes the main change—adding a LICENSE file with Apache 2.0 license text to the repository.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

No actionable comments were generated in the recent review. 🎉

🧹 Recent nitpick comments

LICENSE (1)

190-210: Keep LICENSE text verbatim; move project notice to NOTICE or headers.

The Apache 2.0 license is typically kept unmodified, with project-specific notices placed in a NOTICE file or per-file headers. Appending the Supabase notice inside LICENSE can create ambiguity about whether the license text has been altered and invites future merge churn.

♻️ Suggested change (keep LICENSE verbatim)

-   Copyright 2025 Supabase
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0

Consider placing the removed block in a new NOTICE file or in source file headers instead.

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}