Unfortunately, git.fsfe.org/fsfe-system-hackers/synapse 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.
To add the badge to your project's README.md
file,
use the following snippet:
[![REUSE status](https://api.reuse.software/badge/git.fsfe.org/fsfe-system-hackers/synapse)](https://api.reuse.software/info/git.fsfe.org/fsfe-system-hackers/synapse)
The API provides machine-readable artifacts for automatic analysis.
reuse spdx
command.
Commit fd28d6bc93f07be484d2515ff7072e62c05a6cee
was checked on 23 Feb 2024 02:38:17 UTC
with the following result:
# MISSING COPYRIGHT AND LICENSING INFORMATION The following files have no copyright and licensing information: * roles/docker/tasks/main.yml * roles/hookshot/files/passkey.pem * roles/hookshot/meta/main.yml * roles/hookshot/tasks/main.yml * roles/hookshot/templates/config.yml * roles/hookshot/templates/registration.yml * roles/synapse/templates/synapse/appservices/bifrost.yaml * roles/synapse/templates/synapse/appservices/hookshot.yaml # SUMMARY * Bad licenses: 0 * Deprecated licenses: 0 * Licenses without file extension: 0 * Missing licenses: 0 * Unused licenses: 0 * Used licenses: CC0-1.0, BSD-2-Clause, MPL-2.0, GPL-3.0-or-later * Read errors: 0 * files with copyright information: 34 / 42 * files with license information: 34 / 42 Unfortunately, your project is not compliant with version 3.0 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-Identifer' tags to each file. The tutorial explains additional ways to do this: <https://reuse.software/tutorial/>