REUSE compliance of utilities/keysmith

Unfortunately, invent.kde.org/utilities/keysmith 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/invent.kde.org/utilities/keysmith)](https://api.reuse.software/info/invent.kde.org/utilities/keysmith)

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 7be09158d0c6d52c686dfbdf6bab04d957354569 was checked on 11 Oct 2025 16:34:04 UTC with the following result: 

warning: redirecting to https://invent.kde.org/utilities/keysmith.git/
# MISSING LICENSES

'LGPL-2.1-only' found in:
* po/ca@valencia/keysmith.po
* po/uk/keysmith.po
'LGPL-2.1-or-later' found in:
* src/stateconfig.kcfgc
'LGPL-3.0-only' found in:
* po/ca@valencia/keysmith.po
* po/uk/keysmith.po
'LicenseRef-KDE-Accepted-LGPL' found in:
* po/ca@valencia/keysmith.po
* po/uk/keysmith.po

# SUMMARY

* Bad licenses: 0
* Deprecated licenses: 0
* Licenses without file extension: 0
* Missing licenses: LGPL-2.1-only, LGPL-2.1-or-later, LGPL-3.0-only, LicenseRef-KDE-Accepted-LGPL
* Unused licenses: 0
* Used licenses: BSD-2-Clause, BSD-3-Clause, CC-BY-SA-4.0, CC0-1.0, GPL-3.0-or-later, LGPL-2.1-only, LGPL-2.1-or-later, LGPL-3.0-only, LicenseRef-KDE-Accepted-LGPL
* Read errors: 0
* Invalid SPDX License Expressions: 0
* Files with copyright information: 237 / 237
* Files with license information: 237 / 237

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.