Need help with nlf?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

iandotkelly
130 Stars 35 Forks Other 195 Commits 19 Opened issues

Description

Node License Finder

Services available

!
?

Need anything else?

Contributors list

# 256,526
HTML
a11y
Shell
CSS
143 commits
# 21,673
C
unix
clean-c...
node-js
8 commits
# 100,812
node
soap-cl...
HTML
gitlab
4 commits
# 294,392
HTML
openapi
CSS
convent...
3 commits
# 757,394
JavaScr...
Shell
2 commits
# 17,154
JavaScr...
templat...
node
coffees...
2 commits
# 20,436
Terrafo...
React N...
kafka
Electro...
1 commit
# 71,800
React
scrollb...
Kotlin
google-...
1 commit
# 3,175
Swift
viml
vim-scr...
Kotlin
1 commit
# 653,695
JavaScr...
Shell
TypeScr...
1 commit
# 46,474
Objecti...
cssinjs
js
React
1 commit
# 25,586
Shell
TypeScr...
Less
rich-te...
1 commit
# 125,450
Shell
csv-par...
Common ...
OCaml
1 commit

Node License Finder (nlf)

Version Downloads Build Status Known Vulnerabilities Coveralls

nlf is a utility for attempting to identify the licenses of modules in a node.js project.

It looks for license information in package.json, readme and license files in the project. Please note, in many cases the utility is looking for standard strings in these files, such as MIT, BSD, Apache, GPL etc - this is not error free, so if you have any concerns at all about the accuracy of the results, you will need to perform a detailed manual review of the project and its dependencies, reading all terms of any included or referenced license.

Use

nlf can be used programmatically, or from the command line.

Options

  • -c
    ,
    --csv
    (Default:false) - output in csv format
  • -d
    ,
    --no-dev
    (Default:false) - exclude development dependencies
  • -r
    ,
    --reach
    (Default: Infinity) - package depth (reach), 0 is current package.json file only
  • -s
    ,
    --summary off|simple|detail
    (Default: simple) - summary information, not available in csv format

CLI

To install:

$ npm install -g nlf

To use:

$ cd my-module
$ nlf

Example output:

[email protected] [license(s): MIT/X11]
└── package.json:  MIT/X11

[email protected] [license(s): MIT] └── readme files: MIT

[email protected] [license(s): BSD] ├── package.json: BSD └── license files: BSD

[email protected] [license(s): BSD] ├── package.json: BSD └── license files: BSD

[email protected] [license(s): BSD] └── license files: BSD

[email protected] [license(s): MIT] └── readme files: MIT

LICENSES: BSD, MIT, MIT/X11

For output in CSV format use the -c (or --csv) switch:

$ cd my-module
$ nlf -c

To exclude development dependencies and only analyze dependencies for production:

$ cd my-module
$ nlf -d

Summary Mode

--summary 
option, which can be set to "off", "simple" or "detail". This option controls what will be printed in summary in standard format.
  • off
    turns off summary output
  • simple
    shows a list of licenses used in the project, the default behavior
  • detail
    shows all modules in current project and group by licenses. As example below:
LICENSES:
├─┬ BSD
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ └── [email protected]
├─┬ BSD-2-Clause
│ └── [email protected]
├─┬ Apache-2.0
│ ├── [email protected]
│ ├── [email protected]
│ └── [email protected]
├─┬ (MIT AND CC-BY-3.0)
│ └── [email protected]
└─┬ MPL
  └── [email protected]

Programmatically

var nlf = require('nlf');

nlf.find({ directory: '/User/me/my-project' }, function (err, data) { // do something with the response object. console.log(JSON.stringify(data)); });

// to only include production dependencies nlf.find({ directory: '/User/me/my-project', production: true }, function (err, data) { // do something with the response object. console.log(JSON.stringify(data)); });

The data returned from find() is an array of modules, each of which is represented by an object as the following example:

{
  "id": "[email protected]",
  "name": "example",
  "version": "0.2.9",
  "repository": "http:\/\/github.com\/iandotkelly\/example",
  "directory": "\/Users\/ian\/example",
  "licenseSources": {
    "package": {
      "sources": [
        {
          "license": "MIT",
          "url": "http://opensource.org/MIT"
        }
      ]
    },
    "license": {
      "sources": [
        {
          "filePath": "\/Users\/ian\/Personal\/example\/LICENSE",
          "text": "the text of the license file",
          "names": function() { // function that returns the name of the license if known }
        }
      ]
    },
    "readme": {
      "sources": [
        {
          "filePath": "\/Users\/ian\/Personal\/example\/readme.md",
          "text": "text of the readme"
          "names": function() { // function that returns the name of the license if known }
        }
      ]
    }
  }
}

Each

Tests

To run the unit tests, install development dependencies and run tests with 'gulp'. Requires gulp.js to be installed globally.

# only need to install gulp if you have not done so already
$ npm install -g gulp
$ cd nlf
$ npm install
$ gulp

If you contribute to the project, tests are written in mocha, using should.js or the node.js assert module.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.