REUSE compliance of fsfe-system-hackers/docker-pipenv

Unfortunately, git.fsfe.org/fsfe-system-hackers/docker-pipenv 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/git.fsfe.org/fsfe-system-hackers/docker-pipenv)](https://api.reuse.software/info/git.fsfe.org/fsfe-system-hackers/docker-pipenv)

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 f913aa562e7730172cd3f63f83c69bdb07af42c8 was checked on 22 Dec 2025 11:27:41 UTC with the following result:

# MISSING LICENSES

'CC0-1.0' found in:
* .drone.yml

# 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-or-later
* Read errors: 0
* Invalid SPDX License Expressions: 0
* Files with copyright information: 6 / 6
* Files with license information: 6 / 6

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.