REUSE compliance of nextcloud/circles

Unfortunately, github.com/nextcloud/circles is not REUSE compliant and does not fully adopt the recommendations to make software licensing easy for humans and machines alike. Have a look at our tutorial to learn about the three simple steps to become REUSE compliant.

Badge

To add the badge to your project's README.md file, use the following snippet:

[![REUSE status](https://api.reuse.software/badge/github.com/nextcloud/circles)](https://api.reuse.software/info/github.com/nextcloud/circles)

Machine-readable information

The API provides machine-readable artifacts for automatic analysis.

• All information about the latest compliance check can also be accessed via a machine-parsable JSON file.
• You can gather the automatically generated SPDX SBOM in Tag:Value format, based on the reuse spdx command.

Last lint output

Commit b04ed47547e6fc4d860808d04e8b5caed3c3bbdb was checked on 20 Jul 2026 00:52:04 UTC with the following result:

# MISSING COPYRIGHT AND LICENSING INFORMATION

The following files have no copyright and licensing information:
* .l10nignore

# SUMMARY

* Bad licenses: 0
* Deprecated licenses: 0
* Licenses without file extension: 0
* Missing licenses: 0
* Unused licenses: 0
* Used licenses: AGPL-3.0-only, AGPL-3.0-or-later, Apache-2.0, BSD-3-Clause, CC0-1.0, GPL-3.0-or-later, ISC, MIT, MPL-2.0
* Read errors: 0
* Invalid SPDX License Expressions: 0
* Files with copyright information: 859 / 860
* Files with license information: 859 / 860

Unfortunately, your project is not compliant with version 3.3 of the REUSE Specification :-(


# RECOMMENDATIONS

* Fix missing copyright/licensing information: For one or more files, the tool
  cannot find copyright and/or licensing information. You typically do this by
  adding 'SPDX-FileCopyrightText' and 'SPDX-License-Identifier' tags to each
  file. The tutorial explains additional ways to do this:
  <https://reuse.software/tutorial/>