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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@lowdep/license-gen

v1.0.0

Published

Generate a LICENSE file (MIT, Apache-2.0, BSD, ISC, 0BSD, Unlicense) with author/year filled in — fully offline, zero dependencies

Readme

license-gen

Zero dependencies Node License: MIT Platform

Generate a LICENSE file from your terminal — fully offline. Fills in the copyright holder and year automatically (from your git config), and bundles the full text of the most common open-source licenses. Zero dependencies.

No network call, no API, no dependency tree — just the license text written to disk.


Install

npm install -g license-gen

Or without installing:

npx license-gen mit

Usage

license-gen mit                       # MIT, author auto-detected from git
license-gen apache-2.0 -n "Jane Doe"  # Override the name
license-gen isc -y 2024               # Override the year
license-gen mit --stdout              # Preview without writing
license-gen mit --force               # Overwrite an existing LICENSE
license-gen --list                    # List available licenses

Example

$ license-gen mit

✓ Created LICENSE  (MIT)
  Copyright (c) 2026 Jane Doe

The author name is resolved in this order:

  1. --name flag
  2. git config user.name
  3. package.jsonauthor
  4. your OS username

Available Licenses

| Key | License | SPDX | |---|---|---| | mit | MIT License | MIT | | apache-2.0 | Apache License 2.0 | Apache-2.0 | | bsd-2-clause | BSD 2-Clause | BSD-2-Clause | | bsd-3-clause | BSD 3-Clause | BSD-3-Clause | | isc | ISC License | ISC | | 0bsd | BSD Zero Clause | 0BSD | | unlicense | The Unlicense | Unlicense |

Aliases: apacheapache-2.0, bsdbsd-3-clause, bsd2, bsd3.

Not sure which to pick? See choosealicense.com. For most small open-source projects, MIT is the conventional choice.


Options

| Flag | Description | |---|---| | -n, --name <name> | Copyright holder | | -y, --year <year> | Copyright year (default: current) | | -o, --out <file> | Output file (default: LICENSE) | | --stdout | Print to stdout instead of writing | | --force | Overwrite an existing file | | -l, --list | List available licenses |


License

MIT


Keywords

license generator · generate license · mit license · apache license · choose a license · license file · open source license · spdx · offline · zero dependencies


Built to solve, shared to help — Rushabh Shah 🛠️✨

One of 40+ zero-dependency developer CLI tools — no node_modules, ever.