license-checker alternatives and similar modules
Based on the "Command Line Apps" category.
Alternatively, view license-checker alternatives based on common mentions on social networks and blogs.
-
ignite
Infinite Red's battle-tested React Native project boilerplate, along with a CLI, component/model generators, and more! 9 years of continuous development and counting. -
David
:eyeglasses: Node.js module that tells you when your package npm dependencies are out of date. -
Whatspup
:white_square_button: WhatsApp chat from commandline/console/cli using GoogleChrome puppeteer -
tty-table
Terminal table for Windows, Linux, and MacOS. Written in nodejs. Also works in browser console. Word wrap, padding, alignment, colors, Asian character support, per-column callbacks, and you can pass rows as objects or arrays. Backwards compatible with Automattic/cli-table.
CodeRabbit: AI Code Reviews for Developers
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of license-checker or a related project?
README
NPM License Checker
As of v17.0.0 the failOn
and onlyAllow
arguments take semicolons as delimeters instead of commas. Some license names contain
commas and it messed with the parsing
Ever needed to see all the license info for a module and its dependencies?
It's this easy:
npm install -g license-checker
mkdir foo
cd foo
npm install yui-lint
license-checker
You should see something like this:
ββ [email protected]
β ββ repository: http://github.com/chriso/cli
β ββ licenses: MIT
ββ [email protected]
β ββ repository: https://github.com/isaacs/node-glob
β ββ licenses: UNKNOWN
ββ [email protected]
β ββ repository: https://github.com/isaacs/node-graceful-fs
β ββ licenses: UNKNOWN
ββ [email protected]
β ββ repository: https://github.com/isaacs/inherits
β ββ licenses: UNKNOWN
ββ [email protected]
β ββ licenses: MIT
ββ [email protected]
β ββ repository: https://github.com/isaacs/node-lru-cache
β ββ licenses: MIT
ββ [email protected]
β ββ repository: https://github.com/isaacs/node-lru-cache
β ββ licenses: MIT
ββ [email protected]
β ββ repository: https://github.com/isaacs/minimatch
β ββ licenses: MIT
ββ [email protected]
β ββ repository: https://github.com/isaacs/minimatch
β ββ licenses: MIT
ββ [email protected]
β ββ repository: https://github.com/isaacs/sigmund
β ββ licenses: UNKNOWN
ββ [email protected]
ββ licenses: BSD
ββ repository: http://github.com/yui/yui-lint
An asterisk next to a license name means that it was deduced from an other file than package.json (README, LICENSE, COPYING, ...) You could see something like this:
ββ [email protected]
ββ repository: https://github.com/visionmedia/debug
ββ licenses: MIT*
Options
--production
only show production dependencies.--development
only show development dependencies.--start [path of the initial json to look for]
--unknown
report guessed licenses as unknown licenses.--onlyunknown
only list packages with unknown or guessed licenses.--json
output in json format.--csv
output in csv format.--csvComponentPrefix
prefix column for component in csv format.--out [filepath]
write the data to a specific file.--customPath
to add a custom Format file in JSON--exclude [list]
exclude modules which licenses are in the comma-separated list from the output--relativeLicensePath
output the location of the license files as relative paths--summary
output a summary of the license usage',--failOn [list]
fail (exit with code 1) on the first occurrence of the licenses of the semicolon-separated list--onlyAllow [list]
fail (exit with code 1) on the first occurrence of the licenses not in the semicolon-seperated list--packages [list]
restrict output to the packages (package@version) in the semicolon-seperated list--excludePackages [list]
restrict output to the packages (package@version) not in the semicolon-seperated list--excludePrivatePackages
restrict output to not include any package marked as private--direct look for direct dependencies only
Exclusions
A list of licenses is the simplest way to describe what you want to exclude.
You can use valid SPDX identifiers.
You can use valid SPDX expressions like MIT OR X11
.
You can use non-valid SPDX identifiers, like Public Domain
, since npm
does
support some license strings that are not SPDX identifiers.
Examples
license-checker --json > /path/to/licenses.json
license-checker --csv --out /path/to/licenses.csv
license-checker --unknown
license-checker --customPath customFormatExample.json
license-checker --exclude 'MIT, MIT OR X11, BSD, ISC'
license-checker --packages '[email protected];[email protected];[email protected]'
license-checker --excludePackages 'internal-1;internal-2'
license-checker --onlyunknown
Custom format
The --customPath
option can be used with CSV to specify the columns. Note that
the first column, module_name
, will always be used.
When used with JSON format, it will add the specified items to the usual ones.
The available items are the following:
- name
- version
- description
- repository
- publisher
- url
- licenses
- licenseFile
- licenseText
- licenseModified
You can also give default values for each item. See an example in [customFormatExample.json](customFormatExample.json).
Requiring
var checker = require('license-checker');
checker.init({
start: '/path/to/start/looking'
}, function(err, packages) {
if (err) {
//Handle error
} else {
//The sorted package data
//as an Object
}
});
Debugging
license-checker uses debug for internal logging. Thereβs two internal markers:
license-checker:error
for errorslicense-checker:log
for non-errors
Set the DEBUG
environment variable to one of these to see debug output:
$ export DEBUG=license-checker*; license-checker
scanning ./yui-lint
ββ [email protected]
β ββ repository: http://github.com/chriso/cli
β ββ licenses: MIT
# ...
How Licenses are Found
We walk through the node_modules
directory with the read-installed
module. Once we gathered a list of modules we walk through them and look at all of their package.json
's, We try to identify the license with the spdx
module to see if it has a valid SPDX license attached. If that fails, we then look into the module for the following files: LICENSE
, LICENCE
, COPYING
, & README
.
If one of the those files are found (in that order) we will attempt to parse the license data from it with a list of known license texts. This will be shown with the *
next to the name of the license to show that we "guessed" at it.
*Note that all licence references and agreements mentioned in the license-checker README section above
are relevant to that project's source code only.