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 🙏

© 2024 – Pkg Stats / Ryan Hefner

mklicense

v0.1.5

Published

CLI tool for building Licenses files. Easily.

Downloads

20

Readme

mklicense MIT license Travis npm

CLI tool for generating Licenses. Easily.

Stay Tuned :star: :star: :star: :star: :star:

v. 1.0 is coming!

  • mklicense will behave like an old school text-based game, to drive you to which license suits best for your project (thanks Jerod Santo for the idea). But still keeping its value as-is, behaving like a straight-to-the-point tool.

Why should I use this?

  • Licenses are boring;
  • Copy/paste stuff is so 1999;
  • The GitHub LICENSE generator doesn't necessarily includes your information inside the file;
  • It's busy people/beginner's friendly. It doesn't have all those flags to just install a license;
  • You shouldn't trust other people to store your LICENSE sources. LICENSEs are sensible.

Install

$ npm install -g mklicense

Usage

$ mklicense

Since its version 0.1.4, mklicense needs Node version >=4 to run properly.

Licenses included

  • Unlicense
  • MIT
  • Apache 2.0
  • MPL 2.0
  • GNU LGPL 3.0
  • GNU GPL 3.0
  • GNU AGPL 3.0

You talk about trust. So, where are all the licenses located?

mklicense extracts licenses from http://choosealicense.com/ (which is curated by GitHub), and creates a .txt file for your desired project. I have no control over any license, which is a good thing for you and me.

License

MIT © Cezar Augusto