REUSE compliance of fsfe/reuse-docs

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

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 b6decdb4b62d0a38f963b8f7dfb779e25fc0df7a was checked on 06 Jun 2024 20:04:19 UTC with the following result: 

# MISSING LICENSES

'CC-BY-SA-4.0' found in:
* README.md



# SUMMARY

* Bad licenses: 0
* Deprecated licenses: 0
* Licenses without file extension: 0
* Missing licenses: CC-BY-SA-4.0
* Unused licenses: 0
* Used licenses: CC-BY-SA-4.0
* Read errors: 0
* files with copyright information: 1 / 1
* files with license information: 1 / 1

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


# RECOMMENDATIONS

* Fix missing licenses: For at least one of the license identifiers provided by
  the 'SPDX-License-Identifier' tags, there is no corresponding license text
  file in the 'LICENSES' directory. For SPDX license identifiers, you can simply
  run 'reuse download --all' to get any missing ones. For custom licenses
  (starting with 'LicenseRef-'), you need to add these files yourself.