Automated FOSS License Compliance Graphics Graphical files relatde to the tools under “Automated FOSS License Compliance” Building Clean up make clean Build make
Automated FOSS License Compliance
Automated FOSS License Compliance
Automated FOSS License Compliance is a project aiming at providing tools and data to determine license compliance (compatibility and checklists). The outcome will include:
- license classifications
- usage scenarios
- tools using the license classification and usage scenarios
Status
The project started in March 2025.
Current status: ongoing
Outcomes
This project is being migrated from Gitlab and is under restructuring. Sorry for the mess.
Definitions and glossary
Currently being migrated from: https://gitlab.com/automated-foss-license-compliance/foss-license-analysis/-/blob/ap/glossary/glossary_and_definitions.md?ref_type=heads
License classification
By classifying license clauses, rather than only the licenses themselves, and the way components are used and provided, we reduce the complexity of license compliance and compatibility and will provide useful resources for humans and computers. The result of this project can be used to simplify choosing a license for your project, assisting in complying when providing FOSS components to your users, checking compatibility between the licenses in your project.
20 most common FOSS licenses
In this project we’ve set out to classify the 20 most used Open Source licenses. Here are a list of pages and resources about that work:
-
top-20-foss-licenses.md - information about the 20 most used FOSS licenses, including links to JSON files with data, scripts and data to extract the data
-
analysis-report.md - Some words about our analysis of the conditions and permissions in various license resources.
FOSS License Classifications
License classifications is currently being migrated from: https://gitlab.com/automated-foss-license-compliance/foss-license-analysis/-/blob/ap/initial/initial_analysis/initial_analysis.md?ref_type=heads
Who uses and can use the classified licenses:
FOSS License resources
Coming soon.
Tools
SBoM Compliance toolkit
The SBoM Compliance toolkit (soon to be moved to codeberg) is a Python based tool designed to verify compliance of Software Bill of Materials (SBoM). This tools uses Licomp Toolkit (also to be moved to codeberg). Easiest way to install is using pip: pip install sbom-compliance-toolkit.
Licomp toolkit
The Licomp Toolkit is a Python-based utility designed to verify license compatibility between different software components. It serves as a bridge to multiple compatibility resources, allowing developers and legal teams to determine if an inbound license (e.g., a library they want to use) is compatible with their project’s outbound license. Easiest way to install is using pip: pip install licomp-toolkit.
Licomp Automated FOSS License Compliance
These repositories are very much work in progress!
Compiler of the Automated FOSS License Compliance’s matrices producing license compatibility matrices for different usage scenarios using the license classification.
Implementation of Licomp over Automated FOSS License Compliance’s matrices. This will be used by Licomp Toolkit.
Tutorials
Coming up
Presentations
SFSCON 2025
- conference: SFSCON 2025
- presentation: Translate FOSS licenses into code
- slides: pdf
- video: Translate FOSS licenses into code
Sponsors
Automate FOSS License Compliance was funded through the NGI0 Core Fund, a fund established by NLnet with financial support from the European Commission’s Next Generation Internet programme, under the aegis of DG Communications Networks, Content and Technology under grant agreement No 101092990
We set out to provide tools and data to determine license compliance (compatibility and checklists)
- resources with license classifications
- identify use scenarios
- tools using the license resources and scenarios (outside this presentation)
About this page
This page was automatically generated from ssh://git@codeberg.org/software-compliance-org/automated-foss-license-compliance/src/branch/main/README.md