License guide
Free npm License Checker
Check commercial-use verdicts before shipping npm dependencies.
Why check npm licenses?
A package license decides whether you can use, modify, distribute, and sell software that includes that dependency. The first risk is not the direct dependency alone; transitive packages can bring different obligations into a product.
What this tool covers
The current static dataset focuses on 51 common npm packages. The verdict engine recognizes common license families including MIT, Apache-2.0, BSD, ISC, GPL, LGPL, MPL, AGPL, EPL, CC0, and Unlicense. It is intentionally conservative and does not replace legal review.
How to use it
Search a package, read the verdict, then keep the official license text and notices with your release artifacts. Unknown packages should be checked manually on npm and in the source repository.
Check a package
Use the static checker for a quick first-pass verdict, then verify against the official license before release.