Skip to content


Folders and files

Last commit message
Last commit date

Latest commit


Repository files navigation

Open Source License Compliance Handbook

This handbook provides information on how to comply with some of the more common open source licenses under a specific set of use-cases. The goal here is to provide developers and engineers with some "self-serve" information to facilitate the end goal of open source license compliance, as well as identifying some of the more complex open source license compliance aspects for which consultation with open source counsel may be recommended.

Please review DOCUMENTATION before using this handbook.


  1. Fork it (
  2. Create your feature branch (git checkout -b feature/fooBar)
  3. Read our contribution guidelines and Community Code of Conduct
  4. Commit your changes (git commit -am 'Add some fooBar')
  5. Push to the branch (git push origin feature/fooBar)
  6. Create a new Pull Request

NOTE: Commits and pull requests to FINOS repositories will only be accepted from those contributors with an active, executed Individual Contributor License Agreement (ICLA) with FINOS OR who are covered under an existing and active Corporate Contribution License Agreement (CCLA) executed with FINOS. Commits from individuals not covered under an ICLA or CCLA will be flagged and blocked by the FINOS Clabot tool. Please note that some CCLAs require individuals/employees to be explicitly named on the CCLA.

Need an ICLA? Unsure if you are covered under an existing CCLA? Email

License and Contributions

Copyright 2018-2019 Fintech Open Source Foundation (FINOS), Jilayne Lovejoy, and other contributors.

The compliance handbook and license compliance data is licensed under CC-BY-SA-4.0. Software source code is licensed under Apache-2.0.


Huge thanks to Jilayne Lovejoy, who did the lion's share of the work on the to get the first version of the handbook out the door, and compiled the initial license compliance info. Aaron Williamson of FINOS conceived of the project, designed the YAML format for license info, and wrote the script to process the YAML into different outputs.

Additional thanks Heather Meeker, Gary O'Neall, and Carlo Piana for reviewing the project before release and their invaluable feedback and contributions!


A data store and handbook of practical information about complying with the most common open source licenses.



Unknown, Apache-2.0 licenses found

Licenses found






No packages published