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

@guidesmiths/license-checker

v2.1.0

Published

Audit your NPM dependencies and reject any forbidden license.

Downloads

3,321

Readme

All Contributors

🕵️ Audit your NPM dependencies and reject any forbidden license.

Check our wiki!

Description

This package allows you to do a quick audit on your NPM dependencies by adding it in your hooks.

You can optionally add options to exclude generating the report or avoid generating the error report in case a forbidden license is found (see more details here).

How to use it in your project

  • Install the package

    npm install @guidesmiths/license-checker
  • Add a script to run the package

npx @guidesmiths/license-checker --failOn license1 license2
  • If you are using yarn you may want to run it from the node modules instead of using npx
node_modules/.bin/license-checker --failOn /licenseRegex/
  • Use the script wherever you want (husky hook, in your CI/CD pipeline, ...)

Options

| Option | Description | Type | Default | |---|---|---|---| | --start | Path of the initial json to look for | string | process.cwd() | | --version | Shows the version of the package | string | | | --failOn | Fail (exit with code 1) on the first occurrence of the licenses of the list. If the argument is enclosed in slashes, it will handled like a RegExp | string[] | | | --generateOutputOn | Generates an output file only if any the licenses of the comma-separated list exist (output generated by default) | string | | | --outputFileName | Name of the output file generated | string | license-report-<timestamp>.md | | --errorReportFileName | Name of the file generated when a license in the failOn option is found | string | license-error-<timestamp>.md | | --disableErrorReport | Flag to disable the error report file generation | boolean | false | | --disableReport | Flag to disable the report file generation, whether there is an error or not | boolean | false | | --customHeader | Name of a text file containing the custom header to add at the start of the generated report | string | | | -h, --help | Shows help | boolean | |

Examples

failOn

If the argument is enclosed in slashes, it will be handled like a regular expression where the pattern is the content enclosed. In the following example, license1 is the pattern to test:

npx @guidesmiths/license-checker --failOn /license1/

You may combine both string and regex-like arguments. In this example, license1 will be handled as a RegExp whereas license2 will be handled as a string:

npx @guidesmiths/license-checker --failOn /license1/ license2

Useful links

Contributors ✨

Thanks goes to these wonderful people (emoji key):

This project follows the all-contributors specification. Contributions of any kind welcome!