Go to file
Pablo Rodríguez González ebc6d23e0d Add dist.ini file matcher for Perl modules using Dist::Zilla 2017-01-08 00:39:06 +01:00
bin fix rubocop offenses 2016-09-25 12:35:54 -04:00
docs Add support for the CRAN package manager for R packages. 2016-09-23 10:15:44 -04:00
lib Add dist.ini file matcher for Perl modules using Dist::Zilla 2017-01-08 00:39:06 +01:00
script add integration tests 2016-09-25 19:41:34 -04:00
spec Add dist.ini file matcher for Perl modules using Dist::Zilla 2017-01-08 00:39:06 +01:00
vendor/choosealicense.com expose license rules 2016-11-11 15:02:45 -05:00
.bowerrc initial commit 2014-08-16 12:39:40 -04:00
.coveralls.yml add coveralls 2016-09-25 19:56:53 -04:00
.gitignore expose license rules 2016-11-11 15:02:45 -05:00
.rspec convert tests to rspec 2016-09-25 18:42:36 -04:00
.rubocop.yml disable class length test 2016-03-10 10:32:22 -05:00
.travis.yml set git username and email 2016-09-25 19:52:38 -04:00
CONTRIBUTING.md update documentation 2016-09-22 10:45:17 -04:00
Gemfile drop active support 2016-12-27 15:09:50 -05:00
LICENSE.md fix license encoding 2016-09-25 18:33:13 -04:00
README.md reorder docs in a more logical sequence 2016-10-03 16:08:01 +01:00
licensee.gemspec add coveralls 2016-09-25 19:56:53 -04:00

README.md

Licensee

A Ruby Gem to detect under what license a project is distributed.

Build Status Gem Version Coverage Status

The problem

  • You've got an open source project. How do you know what you can and can't do with the software?
  • You've got a bunch of open source projects, how do you know what their licenses are?
  • You've got a project with a license file, but which license is it? Has it been modified?

The solution

Licensee automates the process of reading LICENSE files and compares their contents to known licenses using a several strategies (which we call "Matchers"). It attempts to determine a project's license in the following order:

  • If the license file has an explicit copyright notice, and nothing more (e.g., Copyright (c) 2015 Ben Balter), we'll assume the author intends to retain all rights, and thus the project isn't licensed.
  • If the license is an exact match to a known license. If we strip away whitespace and copyright notice, we might get lucky, and direct string comparison in Ruby is cheap.
  • If we still can't match the license, we use a fancy math thing called the SørensenDice coefficient, which is really good at calculating the similarity between two strings. By calculating the percent changed from the known license to the license file, you can tell, e.g., that a given license is 95% similar to the MIT license, that 5% likely representing legally insignificant changes to the license text.

Special thanks to @vmg for his Git and algorithmic prowess.

Installation

gem install licensee or add gem 'licensee' to your project's Gemfile.

Documentation

See the docs folder for more information. You may be interested in:

Semantic Versioning

This project conforms to semver. As a result of this policy, you can (and should) specify a dependency on this gem using the Pessimistic Version Constraint with two digits of precision. For example:

spec.add_dependency 'licensee', '~> 1.0'

This means your project is compatible with licensee 1.0 up until 2.0. You can also set a higher minimum version:

spec.add_dependency 'licensee', '~> 1.1'