Free online package.json generator with visual form. Configure project name, version, description, scripts, keywords, dependencies, and more. Select open-source license, set entry point. Pure frontend.
🔒 100% Client-SideThe essential fields are name and version, which uniquely identify every NPM package. Recommended fields include description, main, scripts, keywords, author, and license. For published packages, also include repository, bugs, and homepage.
Common choices: MIT (most permissive, allows commercial use), Apache-2.0 (like MIT with patent protection), GPL-3.0 (copyleft), ISC (like MIT, shorter), BSD-2/3-Clause. When in doubt, go with MIT.
Use semantic versioning MAJOR.MINOR.PATCH. Prefix characters: ^ (compatible within major version), ~ (compatible within patch level), no prefix (exact version), * (any version). Start with 1.0.0 for first stable release.