REUSE compliance of sbabic/libubootenv

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

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 90ed621b679406dc297a74ea68e702dda2f43044 was checked on 14 Nov 2026 21:13:03 UTC with the following result: 

# MISSING LICENSES

'GPL-2.0-only' found in:
* SECURITY.md

# SUMMARY

* Bad licenses: 0
* Deprecated licenses: 0
* Licenses without file extension: 0
* Missing licenses: GPL-2.0-only
* Unused licenses: 0
* Used licenses: CC0-1.0, GPL-2.0-only, LGPL-2.1-or-later, MIT
* Read errors: 0
* Invalid SPDX License Expressions: 0
* Files with copyright information: 23 / 23
* Files with license information: 23 / 23

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.