REUSE compliance of ironcore-dev/dpservice

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

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 f0c0ac0dcb1a03c55d04d31bf3050596695ba1fb was checked on 05 Dec 2025 13:14:46 UTC with the following result:

# MISSING LICENSES

'Apache-2.0")' found in:
* hack/dp_conf_generate.py

# INVALID SPDX LICENSE EXPRESSIONS

'hack/dp_conf_generate.py' contains invalid SPDX License Expressions:
* Apache-2.0")

# MISSING COPYRIGHT AND LICENSING INFORMATION

The following files have no copyright and licensing information:
* src/dp_sync.c

# SUMMARY

* Bad licenses: 0
* Deprecated licenses: 0
* Licenses without file extension: 0
* Missing licenses: Apache-2.0")
* Unused licenses: 0
* Used licenses: Apache-2.0, Apache-2.0")
* Read errors: 0
* Invalid SPDX License Expressions: 1
* Files with copyright information: 474 / 475
* Files with license information: 474 / 475

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.
* 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: