REUSE compliance of kompetenzinventar/ki-ansible

Unfortunately, git.wtf-eg.de/kompetenzinventar/ki-ansible 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/git.wtf-eg.de/kompetenzinventar/ki-ansible)](https://api.reuse.software/info/git.wtf-eg.de/kompetenzinventar/ki-ansible)

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 59a68f9fdbb31a6d9176afca0125908968a371b0 was checked on 16 Apr 2024 17:12:32 UTC with the following result:

# MISSING COPYRIGHT AND LICENSING INFORMATION

The following files have no copyright and licensing information:
* Pipfile
* defaults/main.yml
* templates/docker-compose.yml.j2


# 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
* Read errors: 0
* files with copyright information: 4 / 7
* files with license information: 4 / 7

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