npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

licenz

v0.1.5

Published

Make sure your NPM modules have licenses.

Downloads

2

Readme

licenz

Make sure your NPM modules have licenses.

Installation

Make sure you have Node.js and NPM installed. Then, run the following to use licenz system-wide:

npm install -g licenz

Alternatively, install it as a development dependency in your current module:

npm install licenz --save-dev

Use

CLI

licenz ./path/to/module/

Run licenz --help for additional help.

White-listing Licenses

Does your project’s dependencies have licenses that you know are acceptable? Tell licenz they’re okay by using the --licenses flag:

licenz --licenses "Apache 2, WTFPL, Public Domain" ./path/to/module

White-listing Modules

A are dependencies licenses undetectable by licenz? No problem! Use the --modules flag to make them pass:

licenz --modules "[email protected], module2@^2.1.0" ./path/to/module

Programatically

Licenz exports a single function which you can require:

var licenz = require('licenz');

licenz(options, function(err, res) {
  if (err) {
    console.error(err);
  }
  console.log(res);
});

It expects two optional arguments:

  • options (object): Hash of configurations for licenz. The following keys are used:

    • path (string): Path to the directory to scan. Example:

      var options = {
        path: './path/to/module'
      };
    • whitelistLicenses (array): List of licenses to accept. Example:

      var options = {
        whitelistLicenses: ['My Cool License', 'My Other License']
      };
    • whitelistModules (object): List of modules to accept. Use module names as the keys and corresponding semver-compatible versions or ranges as the values:

      var options = {
        whitelistModules: {
          'my-module': '^2.3.0',
          'my-other-module': '0.5.2',
          'my-best-module': '~8.0.0'
        }
      };
  • callback (function): Node-style callback function. The “response” is an array of unlicensed module objects. A possible way of dealing with it:

    licenz(options, function(err, res) {
      if (err) {
        return console.error(err);
      }
      if (res.length) {
        res.forEach(function(module) {
          console.log('Unlicensed: ' + module.name + '@' + module.version);
        });
      } else {
        console.log('All licensed!');
      }
    });

    In this example, res would be populated with these objects:

    {
      licenses: 'UNKNOWN',
      licenseFile: undefined,
      name: 'unlicensed-module'
      repository: 'https://github.com/unlicensed-user/unlicensed-module',
      version: '1.0.0'
    }

licenz also supports a Promise interface:

licenz(options).then(function(results) {
  console.log(results);
}).catch(function(error) {
  console.error(error);
});

Integrating With Pre-Commit

Integrating licenz with git’s pre-commit hook is easy using pre-commit. Make sure both pre-commit and licenz are installed (npm i pre-commit licenz --save-dev). Then, add a licenz to a script in your package.json:

//...
"scripts": {
  "validate": "licenz",
  //...
}
//...

Then, create a precommit key and add the script:

//...
"precommit": [
  "validate",
  //...
]
//...