REUSE compliance of foundata/ansible-docsmith

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

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 bd0eb60d3a02a6d1212ae6c124c37ecf1d2dab80 was checked on 07 Oct 2025 18:45:46 UTC with the following result: 

# MISSING LICENSES

'`GPL-3.0-or-later`)].' found in:
* ansibledocsmith/src/ansible_docsmith/core/generator.py
'``GPL-3.0-or-later``)].' found in:
* ansibledocsmith/src/ansible_docsmith/core/generator.py

# INVALID SPDX LICENSE EXPRESSIONS

'ansibledocsmith/src/ansible_docsmith/core/generator.py' contains invalid SPDX License Expressions:
* `GPL-3.0-or-later`)].
* ``GPL-3.0-or-later``)].

# SUMMARY

* Bad licenses: 0
* Deprecated licenses: 0
* Licenses without file extension: 0
* Missing licenses: `GPL-3.0-or-later`)]., ``GPL-3.0-or-later``)].
* Unused licenses: 0
* Used licenses: GPL-3.0-or-later, `GPL-3.0-or-later`)]., ``GPL-3.0-or-later``)].
* Read errors: 0
* Invalid SPDX License Expressions: 2
* Files with copyright information: 68 / 68
* Files with license information: 68 / 68

Unfortunately, your project is not compliant with version 3.3 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.
* Fix invalid SPDX License Expressions: In one or more files there are SPDX
  License Expressions which cannot be parse. Check whether the value that
  follows 'SPDX-License-Identifier:' is correct. If the detected expression is
  not meant to be valid, put it between 'REUSE-IgnoreStart' and 'REUSE-
  IgnoreEnd' comments.