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

license-ci-checker

v1.2.0

Published

Checks the compatiblity of your license with your dependencies licenses

Downloads

5

Readme

License CI Checker

license npm version npm downloads

Build Status vulnerabilities

code style: prettier

Disclaimer

I'm not a Lawyer and have very little knowledge about licenses. This code is super simpel, but should help against obvious license violations. I am not responsible for possible misjudgments, false explanations and descriptions

Install

# npm
npm install --save-dev license-ci-checker

# yarn
yarn add -D license-ci-checker

Usage examples

package.json

{
	"scripts": {
		"test-licenses": "license-ci-checker --production"
	}
}

command line

license-ci-checker --production

Options

Most options are passed through from npm-license-crawler.

| param | default | description | | -------------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | --start directory-path | ["./"] | path to the directory the license search should start from. If omitted the current working directory is assumed. Can be declared multiple for multiple entry points. | | --exclude directory-path | [] | path to a directory to be excluded (and its subdirectories) from the search (behaves like --start) | | --unknown | false | show only licenses that can't be determined or have been guessed. | | --dependencies | false | show only third-party licenses, i.e., only list the dependencies defined in package.json. | | --production | false | show only production dependencies | | --development | false | show only development dependencies | | --onlyDirectDependencies | false | show only direct dependencies licenses, i.e., don't list dependencies of dependencies. | | --omitVersion | false | omit version numbers in result (e.g. "[email protected]" becomes "npm-license-crawler") | | --relativeLicensePath | false | output the relative file path for license files. | | --allow | [] | list of packages that doen't throw an error regardless of there license. Like with the --start argument, you can specify it mutliple times |

How does it work?

Licenses can be categorized with a hierarchie. This package checks which license you are using and in which category it belongs. Then it crawls all your licenses dependencies and checks if there licenses are in the same category as yours or below. If not, it throws an error.

License compatiblity

(currently, the implementation is a bit simpler, as explained above)

license categories source: https://janelia-flyem.github.io/

license compatibility source: https://raw.githubusercontent.com/HansHammel/license-compatibility-checker/