REUSE compliance of OSEGermany/OHS-3105

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

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 b48d5d494075b564a2617658ac9f738b1717ced0 was checked on 30 Apr 2025 07:03:54 UTC with the following result:

warning: redirecting to https://gitlab.com/OSEGermany/OHS-3105.git/
# MISSING COPYRIGHT AND LICENSING INFORMATION

The following files have no copyright and licensing information:
* label-sample.svg

# SUMMARY

* Bad licenses: 0
* Deprecated licenses: 0
* Licenses without file extension: 0
* Missing licenses: 0
* Unused licenses: 0
* Used licenses: CC-BY-SA-4.0, CC0-1.0
* Read errors: 0
* Files with copyright information: 12 / 13
* Files with license information: 12 / 13

Unfortunately, your project is not compliant with version 3.3 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-Identifier' tags to each
  file. The tutorial explains additional ways to do this:
  <https://reuse.software/tutorial/>