licensecheck 2022

Output the licenses used by dependencies and check if these are compatible with the project license

LicenseCheck

Output the licences used by dependencies and check if these are compatible with the project license

Table of Contents

• Examples from the command-line
  • Without metprint
  • With metprint
  • Using requirements
  • Failing on packages under MIT license
  • Custom requirements.txt in json format
  • Poetry with dev requirements
• Help
• Configuration Example
  • Example 1: pyproject.toml
  • Example 2: licensecheck.json
  • Example 3: licensecheck.ini
• Documentation
• Install With PIP
• Language information
  • Built for
• Install Python on Windows
  • Chocolatey
  • Windows - Python.org
• Install Python on Linux
  • Apt
  • Dnf
• Install Python on MacOS
  • Homebrew
  • MacOS - Python.org
• How to run
  • Windows
  • Linux/ MacOS
• Download Project
  • Clone
    • Using The Command Line
    • Using GitHub Desktop
  • Download Zip File
• Community Files
  • Licence
  • Changelog
  • Code of Conduct
  • Contributing
  • Security
  • Support
  • Rationale

Examples from the command-line

See below for the output if you run licensecheck in this directory

Without metprint

>> licensecheck
┌──────────┬────────────────────┬────────────────────┐
│Compatible│Package             │License             │
├──────────┼────────────────────┼────────────────────┤
│True      │attrs               │MIT License         │
│True      │certifi             │Mozilla Public Licen│
│True      │charset-normalizer  │MIT License         │
│True      │fhconfparser        │MIT License         │
│True      │idna                │BSD License         │
│True      │metprint            │MIT License         │
│True      │requests            │Apache Software Lice│
│True      │requirements-parser │BSD License         │
│True      │tomlkit             │MIT License         │
│True      │urllib3             │MIT License         │
└──────────┴────────────────────┴────────────────────┘

With metprint

If metprint is installed the tables look slightly different (note that the leftmost symbols are coloured in the terminal)

>> licensecheck
    ┌────────────────────┬──────────────────────────────┐
    │Package             │License                       │
    ├────────────────────┼──────────────────────────────┤
[+] │attrs               │MIT License                   │
[+] │certifi             │Mozilla Public License 2.0 (MP│
[+] │charset-normalizer  │MIT License                   │
[+] │idna                │BSD License                   │
[+] │metprint            │MIT License                   │
[+] │requests            │Apache Software License       │
[+] │requirements-parser │BSD License                   │
[+] │tomlkit             │MIT License                   │
[+] │urllib3             │MIT License                   │
    └────────────────────┴──────────────────────────────┘

Using requirements

>> licensecheck -u requirements
    ┌────────────────────┬──────────────────────────────┐
    │Package             │License                       │
    ├────────────────────┼──────────────────────────────┤
[+] │fhconfparser        │MIT License                   │
[+] │metprint            │MIT License                   │
[+] │pip                 │MIT License                   │
[+] │requests            │Apache Software License       │
[+] │requirements-parser │BSD License                   │
[+] │tomlkit             │MIT License                   │
    └────────────────────┴──────────────────────────────┘

Failing on packages under MIT license

>> licensecheck --fail-licenses mit
    ┌────────────────────┬──────────────────────────────┐
    │Package             │License                       │
    ├────────────────────┼──────────────────────────────┤
[-] │attrs               │MIT License                   │
[+] │certifi             │Mozilla Public License 2.0 (MP│
[-] │charset-normalizer  │MIT License                   │
[-] │fhconfparser        │MIT License                   │
[+] │idna                │BSD License                   │
[-] │metprint            │MIT License                   │
[+] │requests            │Apache Software License       │
[+] │requirements-parser │BSD License                   │
[-] │tomlkit             │MIT License                   │
[-] │urllib3             │MIT License                   │
    └────────────────────┴──────────────────────────────┘

Custom requirements.txt in json format

Add optional path to requirements.txt as outlined in https://github.com/FHPythonUtils/LicenseCheck/issues/9#issuecomment-898878228. Eg. licensecheck --using requirements:c:/path/to/reqs.txt;path/to/other/reqs.txt

>> licensecheck -u 'requirements:requirements.txt;requirements_optional.txt' -f json
{
	"heading": "# Packages - Find a list of packages below",
	"packages": [
			{
					"name": "fhconfparser",
					"version": "2021.1.1",
					"namever": "fhconfparser 2021.1.1",
					"home_page": "https://github.com/FHPythonUtils/FHConfParser",
					"author": "FredHappyface",
					"size": 9241,
					"license": "MIT License",
					"license_compat": true
			},
			...
			{
					"name": "tomlkit",
					"version": "0.7.2",
					"namever": "tomlkit 0.7.2",
					"home_page": "https://github.com/sdispater/tomlkit",
					"author": "S\u00e9bastien Eustace",
					"size": 11653,
					"license": "MIT License",
					"license_compat": true
			}
	]
}

Poetry with dev requirements

Add -u poetry:dev to command-line to include dev packages (excluded by default)

>> licensecheck -u poetry:dev
    ┌────────────────────┬──────────────────────────────┐
    │Package             │License                       │
    ├────────────────────┼──────────────────────────────┤
[+] │attrs               │MIT License                   │
[+] │certifi             │Mozilla Public License 2.0 (MP│
[+] │charset-normalizer  │MIT License                   │
[+] │idna                │BSD License                   │
[+] │metprint            │MIT License                   │
[+] │requests            │Apache Software License       │
[+] │requirements-parser │BSD License                   │
[+] │tomlkit             │MIT License                   │
[+] │urllib3             │MIT License                   │
    └────────────────────┴──────────────────────────────┘

Help

usage: __main__.py [-h] [--format FORMAT] [--file FILE] [--using USING]
                   [--ignore-packages IGNORE_PACKAGES [IGNORE_PACKAGES ...]]
                   [--fail-packages FAIL_PACKAGES [FAIL_PACKAGES ...]]
                   [--ignore-licenses IGNORE_LICENSES [IGNORE_LICENSES ...]]
                   [--fail-licenses FAIL_LICENSES [FAIL_LICENSES ...]] [--zero]

Output the licenses used by dependencies and check if these are compatible with the project license.

optional arguments:
  -h, --help            show this help message and exit
  --format FORMAT, -f FORMAT
                        Output format. one of: json, markdown, csv, ansi, simple. default=simple
  --file FILE, -o FILE  Filename to write to (omit for stdout)
  --using USING, -u USING
                        Environment to use e.g. requirements.txt. one of: requirements, poetry. default=poetry
  --ignore-packages IGNORE_PACKAGES [IGNORE_PACKAGES ...]
                        a list of packages to ignore (compat=True)
  --fail-packages FAIL_PACKAGES [FAIL_PACKAGES ...]
                        a list of packages to fail (compat=False)
  --ignore-licenses IGNORE_LICENSES [IGNORE_LICENSES ...]
                        a list of licenses to ignore (skipped, compat may still be False)
  --fail-licenses FAIL_LICENSES [FAIL_LICENSES ...]
                        a list of licenses to fail (compat=False)
  --zero, -0            Return non zero exit code if an incompatible license is found

You can also import this into your own project and use any of the functions in the DOCS

Configuration Example

Configuration files are parsed in the following order: pyproject.toml, setup.cfg, licensecheck.toml, licensecheck.json, licensecheck.ini, ~/licensecheck.toml, ~/licensecheck.json, ~/licensecheck.ini

• ⚠ All config files are parsed, however configuration defined in previous files takes precedent

Add optional path to requirements.txt as outlined in https://github.com/FHPythonUtils/LicenseCheck/issues/9#issuecomment-898878228 for example: licensecheck --using requirements:c:/path/to/reqs.txt;path/to/other/reqs.txt

Example 1: pyproject.toml

The following config is equivalent to licensecheck -u 'requirements:requirements.txt;requirements_optional.txt' -f json

[tool.licensecheck]
using = "requirements:requirements.txt;requirements_optional.txt"
format = "json"

Example 2: licensecheck.json

The following config is equivalent to licensecheck -u 'requirements:requirements.txt;requirements_optional.txt' -f json

{
	"tool": {
		"licensecheck": {
			"using": "requirements:requirements.txt;requirements_optional.txt",
			"format": "json"
		}
	}
}

Example 3: licensecheck.ini

The following config is equivalent to licensecheck -u 'requirements:requirements.txt;requirements_optional.txt' -f json

[licensecheck]
using = "requirements:requirements.txt;requirements_optional.txt"
format = "json"

Documentation

See the Docs for more information.

Install With PIP

pip install licensecheck

Head to https://pypi.org/project/licensecheck/ for more info

Language information

Built for

This program has been written for Python versions 3.7 - 3.10 and has been tested with both 3.7 and 3.10

Install Python on Windows

Chocolatey

choco install python

Windows - Python.org

To install Python, go to https://www.python.org/downloads/windows/ and download the latest version.

Install Python on Linux

Apt

sudo apt install python3.x

Dnf

sudo dnf install python3.x

Install Python on MacOS

Homebrew

brew install python@3.x

MacOS - Python.org

To install Python, go to https://www.python.org/downloads/macos/ and download the latest version.

How to run

Windows

• Module py -3.x -m [module] or [module] (if module installs a script)

• File py -3.x [file] or ./[file]

Linux/ MacOS

• Module python3.x -m [module] or [module] (if module installs a script)

• File python3.x [file] or ./[file]

Download Project

Clone

Using The Command Line

1. Press the Clone or download button in the top right
2. Copy the URL (link)
3. Open the command line and change directory to where you wish to clone to
4. Type 'git clone' followed by URL in step 2

   git clone https://github.com/FHPythonUtils/LicenseCheck
   

More information can be found at https://help.github.com/en/articles/cloning-a-repository

Using GitHub Desktop

1. Press the Clone or download button in the top right
2. Click open in desktop
3. Choose the path for where you want and click Clone

More information can be found at https://help.github.com/en/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop

Download Zip File

1. Download this GitHub repository
2. Extract the zip archive
3. Copy/ move to the desired location

Community Files

Licence

MIT License Copyright (c) FredHappyface (See the LICENSE for more information.)

Changelog

See the Changelog for more information.

Code of Conduct

Online communities include people from many backgrounds. The Project contributors are committed to providing a friendly, safe and welcoming environment for all. Please see the Code of Conduct for more information.

Contributing

Contributions are welcome, please see the Contributing Guidelines for more information.

Security

Thank you for improving the security of the project, please see the Security Policy for more information.

Support

Thank you for using this project, I hope it is of use to you. Please be aware that those involved with the project often do so for fun along with other commitments (such as work, family, etc). Please see the Support Policy for more information.

Rationale

The rationale acts as a guide to various processes regarding projects such as the versioning scheme and the programming styles used. Please see the Rationale for more information.