Licensed

Licensed caches the licenses of dependencies and checks their status, and is available as a Ruby gem.

Licensed is not a complete open source license compliance solution. Please understand the important disclaimer below to make appropriate use of Licensed.

Current Status

Licensed is currently in low maintenance mode. At this point, we're only looking to maintain this repository for security fixes.

Licensed v4 - Removed support for non-Ruby environments

Licensed v4 no longer provides a self-contained executable build of licensed. Please see the deprecation notice for more context.

Licensed v3

Licensed v3 includes a breaking change if both of the following are true:

1. a project uses bundler to manage ruby dependencies
2. a project uses the self-contained executable build of licensed

All other usages of licensed should not encounter any major changes migrating from the latest 2.x build to 3.0.

See CHANGELOG.md for more details on what's changed. See the v3 migration documentation for more info on migrating to v3.

Licensed v2

Licensed v2 includes many internal changes intended to make licensed more extensible and easier to update in the future. While not too much has changed externally, v2 is incompatible with configuration files and cached records from previous versions. Fortunately, migrating is easy using the licensed migrate command.

See CHANGELOG.md for more details on what's changed. See the v2 migration documentation for more info on migrating to v2, or run licensed help migrate.

Installation

Dependencies

Licensed uses the libgit2 bindings for Ruby provided by rugged. rugged requires cmake and pkg-config which you may need to install before you can install Licensed.

# Ubuntu
sudo apt-get install cmake pkg-config

# macOS
brew install cmake pkg-config

With Gemfile

Add this line to your application's Gemfile:

gem 'licensed', :group => 'development'

And then execute:

$> bundle

With Homebrew (on macOS)

brew install licensed

Usage

See getting started for guidance using Licensed as part of your developer workflow.

Available commands

See the commands documentation for documentation on available commands, or run licensed -h to see all of the current available commands.

Configuration options

A configuration file is required for most commands. See the configuration file documentation for more details on the configuration format and available configuration options.

Available dependency sources

Licensed can enumerate dependency for many languages, package managers, and frameworks. See the sources documentation for the list of currently available sources. Sources can be explicitly enabled and disabled as a configuration option.