Unfortunately, github.com/fossology/fossology 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/github.com/fossology/fossology)
The API provides machine-readable artifacts for automatic analysis.
reuse spdx
command.
Commit 44b9d1d318e7402b17550925e3b25d52aad0f6ac was checked on 17 Mar 2026 14:33:05 UTC
with the following result:
/opt/venv/lib/python3.11/site-packages/reuse/project.py:332: PendingDeprecationWarning: '.reuse/dep5' is deprecated. You are recommended to instead use REUSE.toml. Use `reuse convert-dep5` to convert. warnings.warn( reuse.report - ERROR - Unexpected error occurred while parsing 'NOTICES-THIRDPARTY.html' reuse.exceptions.YearRangeParseError: 'International' is not a valid year range. /opt/venv/lib/python3.11/site-packages/reuse/project.py:332: PendingDeprecationWarning: '.reuse/dep5' is deprecated. You are recommended to instead use REUSE.toml. Use `reuse convert-dep5` to convert. warnings.warn( reuse.report - ERROR - Unexpected error occurred while parsing 'NOTICES-THIRDPARTY.html' reuse.exceptions.YearRangeParseError: 'International' is not a valid year range. # READ ERRORS Could not read: * NOTICES-THIRDPARTY.html # SUMMARY * Bad licenses: 0 * Deprecated licenses: 0 * Licenses without file extension: 0 * Missing licenses: 0 * Unused licenses: 0 * Used licenses: BSD-3-Clause, FSFAP, GPL-2.0-only, LGPL-2.0-only, LGPL-2.1-only, MIT, W3C-19980720 * Read errors: 1 * Invalid SPDX License Expressions: 0 * Files with copyright information: 4549 / 4549 * Files with license information: 4549 / 4549 Unfortunately, your project is not compliant with version 3.3 of the REUSE Specification :-( # RECOMMENDATIONS * Fix read errors: At least one of the files in your directory cannot be read by the tool. Please check the file permissions. You will find the affected files at the top of the output as part of the logged error messages.