ros-license-toolkit 1.1.4

Checks ROS packages for correct license declaration.

ros_license_toolkit

Warning For any legal questions, please consult a lawyer. This tool is not a substitute for legal advice.

Motivation

ROS packages must have licenses. This tool checks if the license declarations in the package.xml matches the license(s) of the code. We do this by using scancode-toolkit to scan the code and compare the results to the declaration in the package.xml

Functionality

graph TD
    classDef stroke stroke:#333,stroke-width:2px;
    s([scan code for licenses and copyrights]) 
    class s stroke
    p[compare to\n package.xml\nfor linting]
    class p stroke
    c[create\ncopyright file\nfor release]
    class c stroke
    s --> p
    s --> c

Features

This checks:

• Is any license defined in package.xml? - LicenseTagExistsCheck
• Has at most one license tag without a source-files declaration? - LicenseTagExistsCheck
• Do all licenses tags follow the SPDX standard? - LicenseTagIsInSpdxListCheck
• Are license texts available and correctly referenced for all declared licenses? - LicenseTextExistsCheck
• Does the code contain licenses not declared in any license tags source-file attribute (source-files="src/something/**")? - LicensesInCodeCheck

Usage

Installation

Install the package from source:

pip install .

Basic Usage

You should then have the executable in your $PATH and can run it on any ROS package or a directory containing multiple ROS packages:

ros_license_toolkit my_ros_package

All Options

$ ros_license_toolkit -h
usage: ros_license_toolkit [-h] [-c] [-v] [-q] path

Checks ROS packages for correct license declaration.

positional arguments:
  path                  path to ROS2 package or repo containing packages

optional arguments:
  -h, --help            show this help message and exit
  -c, --generate_copyright_file
                        generate a copyright file
  -v, --verbose         enable verbose output
  -q, --quiet           disable most output

State of Development

WORK IN PROGRESS This is currently working and feature complete to the point it was originally intended. But there are still open points concerning testing and it is also very important to make sure how this behaves with existing ROS packages. In particular, the following things will have to be done:

To Do

• Coverage analysis
• Linter(s) per CI
• Field trials (check existing ROS packages and see what to do with the results). see field-trials/
• Evaluate runtime. If scancode-toolkit takes too long on too many cases, we will have to look for an alternative.
• Allow license name in tag to be also full name of SPDX key.
• Each LicenseTag should have SPDX id.
• Single license tag without file attribute and single license text should match automatically.
• Turn into github action.

License

ros_license_toolkit is open-sourced under the Apache-2.0 license. See the LICENSE file for details.