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 🙏

© 2025 – Pkg Stats / Ryan Hefner

license-gen

v0.3.4

Published

A interactive generator for opensouce license

Readme

license-gen

type some command to generate a LICENSE file for your project.

Quick Start

$ npm install -g license-gen
cd /path/to/yourproject
license LICENSE_TYPE

Advance

$ license [-a YOURNAME[ -y YEAR[ -p PROJECT[ LINCESE]]]]

eg.

$ license -a Luffy mit
$ license -a Luffy -y 2000 mit

license type can insert into any where of your command:

$ license mit -a Luffy -y 2000

and, if you forget to specify a license type:

$ license -a Luffy

then, it will ask you to input a license type.

So, You really don't need to remember these arguments' requirements.

Alternative

you can use the interactive way to choosing a license. just type the license and press Return key.

and then, finish the questions prompted, you will get a license too.

In the future.

  • append the README file, add license note to the end of the file.
  • much more... I think. :P

Info

  • Inspired by https://www.npmjs.org/package/license.
  • license choosing flow is from http://paulmillr.com/posts/simple-description-of-popular-software-licenses/