Unfortunately, git.fsfe.org/fsfe-system-hackers/drone 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.
To add the badge to your project's README.md
file,
use the following snippet:
[](https://api.reuse.software/info/git.fsfe.org/fsfe-system-hackers/drone)
The API provides machine-readable artifacts for automatic analysis.
reuse spdx
command.
Commit d50cf9b465b7dc4c326610b51c62179969f118b8
was checked on 13 May 2025 19:32:14 UTC
with the following result:
# MISSING LICENSES 'CC0-1.0' found in: * .drone.yml # MISSING COPYRIGHT AND LICENSING INFORMATION The following files have no copyright and licensing information: * .gitignore * renovate.json # SUMMARY * Bad licenses: 0 * Deprecated licenses: 0 * Licenses without file extension: 0 * Missing licenses: CC0-1.0 * Unused licenses: 0 * Used licenses: CC0-1.0, GPL-3.0-only, GPL-3.0-or-later * Read errors: 0 * Files with copyright information: 12 / 14 * Files with license information: 12 / 14 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 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/>