☁️ Nextcloud server, a safe home for all your data
AGPL 3.0
AGPL-3.0GitHub's declared license and a full match of the license text agree.
What this means for you
Share-alike reaches the whole derivative work. Combining it with proprietary code you ship is the classic contamination risk.
- The network clause is the landmine: if users interact with your modified version over a network, you must offer them its source — no distribution required.
- Many companies block AGPL outright in their open-source policy. Check yours before you start.
The repository root holds 2 license files (COPYING, COPYING-README). Projects do this to offer a choice of licenses, or because parts of the tree differ. Read them before you pick.
You can
- Use, study, and modify the code, including commercially
- Distribute your derivative work under the same license
You must
- License the entire derivative work under the same license when you distribute it
- Offer complete corresponding source to anyone who receives a binary
- Keep notices and document your changes
You cannot
- Ship a derivative work as closed source
- Add terms that restrict the freedoms this license grants downstream
- Apply DRM or patent terms that defeat the license's guarantees
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 textFull text match — AGPL-3.0 (100% of the reference text)
Reporight matched the file against the ScanCode LicenseDB reference text for AGPL-3.0. It also resembles SSPL-1.0.
- github apiGitHub declares AGPL-3.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.