REUSE compliance of fif/

Unfortunately, gitlab.com/Lynnesbian/fif/ 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/gitlab.com/Lynnesbian/fif/)](https://api.reuse.software/info/gitlab.com/Lynnesbian/fif/)

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 a570b07672fcb5f3ba87ca00c618c7ef0195477f was checked on 22 Jan 2024 03:35:39 UTC with the following result:

warning: redirecting to https://gitlab.com/Lynnesbian/fif.git/
# MISSING COPYRIGHT AND LICENSING INFORMATION

The following files have no copyright and licensing information:
* .vscode/launch.json


# 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, CC0-1.0, CC-BY-SA-4.0
* Read errors: 0
* files with copyright information: 41 / 42
* files with license information: 41 / 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/>