Grunt task to generate a list of licenses used in a project
Switch branches/tags
Nothing to show
Latest commit d7af256 Mar 21, 2015 @badunk badunk Merge pull request #10 from glarfs/master
support displaying info on screen
Failed to load latest commit information.
tasks support displaying info on screen Oct 10, 2014
test initial commit Apr 25, 2013
.gitignore initial commit Apr 25, 2013
.jshintrc initial commit Apr 25, 2013
.npmignore added npm ignore Apr 25, 2013
Gruntfile.js initial commit Apr 25, 2013
LICENSE-MIT initial commit Apr 25, 2013 Update Apr 26, 2013
package.json support displaying info on screen Oct 10, 2014


Generates a list of recursively dependent licenses used within a project

Getting Started

This plugin requires Grunt ~0.4.1

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-license --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:


The "license" task


In your project's Gruntfile, add a section named license to the data object passed into grunt.initConfig().

  license: {
    options: {
      // Task-specific options go here.
    your_target: {
      // Target-specific file lists and/or options go here.



Type: Boolean Default value: false

Only generate a list of unknown licenses (as opposed to all)


Type: String Default value: .

Project directory from which to start the search


Type: Number Default Value: 1

How deep to search for dependencies. Setting value to null will recurse through all.


Type: String or Array Default Value: all

The types of dependencies to include, such as: ["dependencies", "devDependencies", "peerDependencies"].


Type: String Default Value: LICENSES

The path/filename to write the metadata to (WIP: should eventually output the actual licenses)


In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.