REUSE compliance of bofh69/aoc_2022

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

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 b5fac0a5cd6c8e47abe90cf84a6f60e05aa75bc8 was checked on 14 Jan 2024 05:15:49 UTC with the following result:

The following files have no copyright and licensing information:
* .gitmodules


# SUMMARY

* Bad licenses: 0
* Deprecated licenses: 0
* Licenses without file extension: 0
* Missing licenses: 0
* Unused licenses: 0
* Used licenses: GPL-3.0-or-later
* Read errors: 0
* files with copyright information: 30 / 31
* files with license information: 30 / 31

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