REUSE compliance of semiotic-ai/odos-sdk

Unfortunately, github.com/semiotic-ai/odos-sdk 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/semiotic-ai/odos-sdk)](https://api.reuse.software/info/github.com/semiotic-ai/odos-sdk)

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 20d8d885e055f9913fa51da52095d54a966f37ac was checked on 18 Apr 2026 09:39:05 UTC with the following result:

# MISSING LICENSES

'Apache-2.0` headers (see existing files for the pattern).' found in:
* CLAUDE.md

# INVALID SPDX LICENSE EXPRESSIONS

'CLAUDE.md' contains invalid SPDX License Expressions:
* Apache-2.0` headers (see existing files for the pattern).

# SUMMARY

* Bad licenses: 0
* Deprecated licenses: 0
* Licenses without file extension: 0
* Missing licenses: Apache-2.0` headers (see existing files for the pattern).
* Unused licenses: 0
* Used licenses: Apache-2.0, Apache-2.0` headers (see existing files for the pattern).
* Read errors: 0
* Invalid SPDX License Expressions: 1
* Files with copyright information: 45 / 45
* Files with license information: 45 / 45

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.