REUSE compliance of nextcloud/call_summary_bot

Unfortunately, github.com/nextcloud/call_summary_bot 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/call_summary_bot)](https://api.reuse.software/info/github.com/nextcloud/call_summary_bot)

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 bb2249730cc8df1c0fa5e8c147affe4fdfa0228c was checked on 01 Apr 2026 07:01:27 UTC with the following result:

# MISSING COPYRIGHT AND LICENSING INFORMATION

The following files have no copyright and licensing information:
* .github/workflows/sync-workflow-templates.yml.patch

# SUMMARY

* Bad licenses: 0
* Deprecated licenses: 0
* Licenses without file extension: 0
* Missing licenses: 0
* Unused licenses: 0
* Used licenses: AGPL-3.0-or-later, CC0-1.0, MIT
* Read errors: 0
* Invalid SPDX License Expressions: 0
* Files with copyright information: 251 / 252
* Files with license information: 251 / 252

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/>