How do I check a package's license on npm?

Check the 'license' field in the package's package.json, or view it on the npm website where it's displayed on each package page. You can also run 'npm view license' from the command line.

Can I use npm packages in commercial projects?

It depends on each package's license. MIT-licensed packages (the majority) allow commercial use. GPL packages allow commercial use but may require you to open-source your derivative work. Always verify before shipping.

What does 'UNLICENSED' mean on npm?

UNLICENSED means the author has not granted any license. This is different from 'Unlicense' (public domain). UNLICENSED packages are all rights reserved and technically cannot be used without explicit permission from the author.

npm

Visit npm Compare

https://www.npmjs.com

The world's largest software registry with over 2 million JavaScript packages. Free to use for public packages. Each package has its own license specified in package.json - MIT is the most common, but GPL, Apache, ISC, and proprietary licenses are also used.

npm

Free

Free (Public Registry)

Free

~Depends on package license. Most open-source licenses allow digital use.

~Depends on each package's license field in package.json. MIT (most common) allows commercial use. GPL allows commercial use but requires open-sourcing derivatives. Some packages are proprietary.

~Depends on package license. MIT and Apache allow client work. GPL may require clients to open-source their code.

~Depends on the package license. MIT, Apache, and ISC allow modification. GPL allows modification with share-alike requirements.

Varies

✓Published

Prices may vary by region and are subject to change.

Always check the 'license' field in package.json before using a package. MIT is the most common but not universal - some packages are GPL, proprietary, or have no license specified.
Packages with no license field or 'UNLICENSED' are all rights reserved. You may not have the right to use them in your projects.

All License Details

Hover or tap any field name to see what it means

Field	Value
	✓
	~Depends on each package's license field in package.json. MIT (most common) allows commercial use. GPL allows commercial use but requires open-sourcing derivatives. Some packages are proprietary.
	~Depends on the package license. MIT, Apache, and ISC allow modification. GPL allows modification with share-alike requirements.
	Varies
	✗
	~Depends on the package license. Most open-source licenses allow redistribution with conditions.
	~Depends on package license. Rarely relevant for code packages.
	~Depends on package license. Most open-source licenses allow digital use.
	~Depends on package license. MIT and Apache allow client work. GPL may require clients to open-source their code.
	✓Published
	✗
	✗

Frequently Asked Questions

Informational Only - Not Legal Advice

LicenseOrg provides informational summaries of platform license terms for educational purposes only. This is not legal advice. Always consult the platform’s official license page and a qualified legal professional.

Exclusive perks for members

Join Our Community

Get early access to new features, plus exclusive deals and coupons from top creative platforms.

Compare with…

npm vs GitHub npm vs GitLab npm vs CodeCanyon