hesa/foss-licenses

License meta information

Hi there 👋

📫 How to reach me:

• LinkedIn: henrik-sandklef

foss-licenses's Issues

Add option to list operators

Limited aliases output causes crash

$ flame aliases lists all aliases. To limit the alias output you can use the -l option. This option causes a crash, see below

$ flame aliases -l MIT
usage: flame [-h] [-fc FLAME_CONFIG] [-ld LICENSE_DIR] [-ald ADDITIONAL_LICENSE_DIR] [-lmf LICENSE_MATRIX_FILE] [-ndu] [-of OUTPUT_FORMAT] [-v] [-V] [-d] [-c]
             [--validate-spdx] [--validate-relaxed] [--validate-osadl]
             {license,license-full,compat,simplify,aliases,compats,operators,licenses,unknown} ...
flame: error: ambiguous option: -l could match -ld, -lmf

interpretation of CDDL-1 and CDDL-v1

Can we add an interpretation of "CDDL-1" and "CDDL-v1"?

Markdown output

Add a markdown formatter

Double check versioned licenses

Write tests to check if a license like GPL (without version) is present in GPL-[123]*.json

Python: add option to list supported licenses

Add operator "with"

Add WITH

• with
• w/
• WITH

Remove BSD3-like from BSD-3-Clause

document retured objects

add in license_db.py and PYTHON_API.md a description of the objects returned

Link to disclaimer

Add disclaimer in repo
Add link to the disclaimer in license JSON files

document FOSSLicenses / additional_license_dir

Interpretation of LGPLv2

Can we add an interpretation of "LGPLv2", i.e.

• LGPL-2.0-only, or
• LGPL-2.1-only

add GPL aliases

GPL-3.0-with-GCC-exception

Add alias to Academic

"AFLv2" (Yocto)

Identiy new id for SPDX LicenseRef

Add pypi auto releases

List/verify licenses (not operators) in an expression

Add options to:

• check if licenses are supported by OSADL's matrix e.g. after doing `flame compat x11-keith-packard and BSD3 || GPLv2+"``
• verify license expression (after above)

Allow for list of arguments to license and compat

Today you invoke licensecheck as:flame license "MIT and BSD3" (note the ")
Allow for flame license MIT and BSD (no ")

Document, Readme, order when identifying license

Interpretation of MIT variants

Can we add an interpretation of MIT variants, i.e.

• MIT-X
• MIT-style

Add command "--version"

Cli argument to list all data for a license

List all data, including link to spdx and scan code db. For all licenses

--license l - limits to only output data for license l

Remove versioned licenses without version

Remove the aliases for an existing licenses that has a version (Apache 1, 2 | GPL 1, 2, 3 | MPL 1, 2 .... and so on) but the alias does not have one.

Example. "GNU General Public License" cannot be assumed to be any of the GPL versions. So all "unversioned" aliases like this need to be removed.

Add validation of license

When identifying compatibility_as, using flame compat <license>, you can validate:

• --validate-spdx - Validate that the resulting license expression is valid according to SPDX syntax
• --validate-relaxed - Validate that the resulting license expression is valid according to SPDX syntax, but allow non SPDX identifiers
• --validate-osadl - Validate that the resulting licenses are supported by OSADL's compatibility matrix

It would be useful to have the same possibility when identifying license, using flame license <license>

Fix --validate-spdx option

Currently the option --validate-spdx checks if the licenses are known to [license_expression](https://github.com/nexB/license-expression), which is the same database of licenses as [ScanCode LicenseDB](https://scancode-licensedb.aboutcode.org/.

Instead, a check against should be implemented

• https://spdx.org/licenses/
• https://spdx.org/licenses/exceptions-index.html

Add license Keith Packard License

Add to x11-keith-packard

Interpretation of variants

BSD-3-Clause has variants such Google and Facebook. Other examples

• BSD-like

Adding a compatibility_as would be useful, but what is the most common practice in dealing with these licenses?

Remove multiple blanks from licenses

Apache License Version 2.0 is not the same string as
Apache License Version 2.0, but they refer to the same license.

Suggestion: remove multiple blank before find/replace

add LLVM Exception to Apache 2.0

https://scancode-licensedb.aboutcode.org/llvm-exception.html
https://spdx.org/licenses/LLVM-exception.html

add GCC-exception-3.1

Interpret MPL-1 and MPLv1

Can we add an interpretation of "MPL-1" and "MPLv1"?

Add check if license can be comp checked

Either a license should be supported by the osadl_matrix or have a compatibility_as that is

Add function to check this.

Document API code and write manual

Add organisational information to meta

Suggestion to meta information

• organization
• author

This way a user can chose licenses as submitted by a particular organization.

License alias order incorrect

License aliases are supposed to be replaced longest in size first.

Current solution (license_db.py):
for needle in reversed(collections.OrderedDict(sorted(needles.items()))):
does not do that. Replace the above with:
for needle in reversed(collections.OrderedDict(sorted(needles.items(), key = lambda x : len(x[0])))):

and things should be fine

Don't use scancode_key as aliases

Problem
Currently x11 gets normalized to ICU

$ flame --verbose license x11
ICU
 * "x11" -> "ICU via "scancode"

This is the case since the scancode_key is automatically added as an alias and for ICU the scancode_key is x11.

Solution
In Python: do not look for the scancode_key when identifying the license
in JSON license files: add relevant scancode_keys to alias list (e.g. not x11 for ICU)

Allow different quote signs

Treat the following the same: ', ", “

Suggestion: replace ',“ with "
Perhaps match beginning and ending quote

Interpretation of PSF

Can we add an interpretation of PSF, i.e.

• Python-2.0

Create pypi package

Chose license for "lib"

add Apache-2.0 alias

Apache Software License (Apache-2.0)
Apache Software License (Apache License, Version 2.0)

Add command to list compounds

Document problematic licenses/operators

Problematic names of licenses

• MPL
• EPL
• GPL
• LGPL
• BSD License (BSD License)
• BSD License (new BSD)
• Apache Software License
• OSI Approved :: Apache Software License
• PSL (Python Software License)
• PSL, PSF, PSFL, PSF License, PSF License Agreement, Python license, Python Software Foundation License
• ASL
• Public (is this "Public-Domain"?)

Possible operators

Is there an interpretation for the following: + /

Document how to extend with your own license files (etc)

Complex license expression produces incorrect compat

The following command's output is incorrect:

$ flame compat "x11-keith-packard and Apache Software License, Ve rsion 2.0 | mit"
(LicenseRef-flame-x11-keith-packard AND Apache-2.0) OR MIT

should be:

$ flame compat "x11-keith-packard and Apache Software License, Ve rsion 2.0 | mit"
(HPND AND Apache-2.0) OR MIT

add BSD-* aliases

BSD 2-Clause "Simplified"

BSD-3-clause New
BSD 3-Clause "New"
BSD 3-Clause New

Allow for user defined (additional) license info

Useful when a company have their own license id (spdx license ref) and want to map that to a license in osadl or elmat

Ambiguity alias with "and" fails to identify the ambiguity

Common Development and Distribution License (CDDL) is an alias for the ambiguity Common Development and Distribution License. An ambiguity should create a warning for the user (about the ambiguity) but a parse exception is raised instead.

$ flame license "Common Development and Distribution License (CDDL)"
Error: Could not parse "Common Development  AND  Distribution License  ( CDDL )". Exception: Invalid expression nesting such as (AND xx) for token: "(" at position: 47

Preferably the exception should be caught and the user should be warned about both:

• the license could not be parsed
• the license has an ambiguity

Note: it is "and" that causes the problem in the above example since "and" is part of the license syntax (e.g. MIT AND BSD-3-Clause)