This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Reason given by maintainers: liccheck is up to date now
Python License Checker
Check python packages from requirement.txt and report license issues.
About
You can define a list of authorized licenses, authorized packages, unauthorized licenses.
The tool will check the requirement.txt files, check packages and their dependencies and return an error if some packages are not compliant against the strategy. A package is considered as not compliant when its license is in the unauthorized license list or is unknown. A package is considered as compliant when its license is in authorized license list, or if the package is itself in the list of authorized packages.
How to install
$ pip install liccheck
How to use
liccheck will read the requirement.txt and check packages agains a strategy defined in the ini file. If the file is not specified on command line, it will lookup for requirement.txt in the current folder. You have to setup an ini file with an authorized license list, unauthorized license list, authorized package list.
Here is an example of a strategy:
# Authorized and unauthorized licenses in LOWER CASE
[Licenses]
authorized_licenses:
bsd
new bsd
bsd license
new bsd license
simplified bsd
apache
apache 2.0
apache software license
gnu lgpl
lgpl with exceptions or zpl
isc license
isc license (iscl)
mit
mit license
python software foundation license
zpl 2.1
unauthorized_licenses:
gpl v3
[Authorized Packages]
# Python software license (see http://zesty.ca/python/uuid.README.txt)
uuid: 1.30
For demo purpose, let’s say your requirement.txt file contains this:
Flask>=0.12.1 flask_restful jsonify psycopg2>=2.7.1 nose scipy scikit-learn pandas numpy argparse uuid sqlbuilder proboscis pyyaml>=3.12
The execution will output this:
$ liccheck -s my_strategy.ini -r my_project/required.txt gathering licenses...23 packages and dependencies. check forbidden packages based on licenses...none check authorized packages based on licenses...19 packages. check authorized packages...4 packages. check unknown licenses...none
If some dependencies are unknown or are not matching strategy, the output will be something like:
$ liccheck -s my_strategy.ini -r my_project/required.txt
gathering licenses...32 packages and dependencies.
check forbidden packages based on licenses...1 forbidden packages :
Unidecode (0.4.21) : GPL ['GNU General Public License v2 or later (GPLv2+)']
dependencye(s):
Unidecode << python-slugify << yoyo-migrations
check authorized packages based on licenses...24 packages.
check authorized packages...6 packages.
check unknown licenses...1 unknown packages :
feedparser (5.2.1) : UNKNOWN []
dependencye(s):
feedparser
Licensing
See LICENSE
Metadata
Release files for liccheck2 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| liccheck2-0.1.4.tar.gz | 5.7 kB | Without provenance | Details for liccheck2-0.1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| liccheck2-0.1.4-py3-none-any.whl | Python 3 | none | any | Details for liccheck2-0.1.4-py3-none-any.whl |
Total release size: 12.4 kB
Release files / liccheck2-0.1.4.tar.gz
| Download URL | liccheck2-0.1.4.tar.gz |
|---|---|
| Size | 5.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3186602ed85da3808a98ec5e5248e39a63b4f50beb40d45695ab15b00b3e2417
|
|
BLAKE2b-256 checksum How to use checksums |
1293472e81229c5981c48e377a5c89841f19ba3066c037cb50dc95eceeb88f16
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / liccheck2-0.1.4-py3-none-any.whl
| Download URL | liccheck2-0.1.4-py3-none-any.whl |
|---|---|
| Size | 6.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
93c5dab46c737ada221c119d3a43b837397c806e64e8657427c8b3ed50482f3d
|
|
BLAKE2b-256 checksum How to use checksums |
8fe9e626f73a43b9c71730a70ec2bcc4e87a7ed75d9b9dd6beaedf9d1b0fc616
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for liccheck2 0.1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.