Empowering everyone to build reliable and efficient software.
Apache 2.0
Apache-2.0GitHub's declared license is corroborated by a partial match of the license text (the file is likely reformatted or trimmed).
What this means for you
Broad reuse — including inside proprietary products — in exchange for keeping notices intact.
- Ships an express patent grant — and terminates it if you sue a contributor over patents in this work.
- If the project has a NOTICE file, you must pass it along with your distributions.
- You must mark files you changed.
The repository root holds 2 license files (LICENSE-APACHE, LICENSE-MIT). Projects do this to offer a choice of licenses, or because parts of the tree differ. Read them before you pick.
You can
- Use the code commercially, privately, and inside closed-source products
- Modify it and distribute your modified version
- Sublicense it as part of a larger work under your own terms
You must
- Keep the original copyright notice and license text with copies you distribute
- State the license of the incorporated code in your distribution or docs
You cannot
- Strip required notices or claim you wrote the original work
- Expect a warranty, support, or liability cover from the authors
- Imply the authors endorse your product
This is not legal advice. Your obligations depend on how you use the code and your jurisdiction. Consult counsel for production risk.
How we know
- exact textLICENSE-MIT is MIT
A full match against the ScanCode reference text for MIT. GitHub's own detector did not report this file.
- partial textPartial text match — Apache-2.0 (90% of the reference text)
Reporight matched the file against the ScanCode LicenseDB reference text for Apache-2.0.
- github apiGitHub declares Apache-2.0
GitHub runs its own detector (licensee) over the repository root and publishes the result in its API.
This summary reads the repository root only. Vendored trees and per-file headers can differ — run a deep scan to map every file.