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-server

v1.0.0

Published

This is a server which is used to watch repos at Jam3 and output the license of a repo

Readme

license-server

experimental

A server which watches your organization and outputs license information for repos which contain a package.json file.

Usage

NPM:

NPM

Deploy onto Heroku:

Deploy

When deploying to Heroku a few environment variables are required:

org

The organization where repos to be checked are.

gitToken

This is an api access token to communicate with Github.

To create your personal github access token go here:

  1. https://github.com/settings/tokens
  2. Press "Generate Token"
  3. Ensure "repo" is checked (nothing else is needed)

gitHookSecret:

This is a secret token value for Github to communicate via webhooks.

  1. Visit your orgs settings/hooks at this link: https://github.com/organizations/[Your Org Here]/settings/hooks
  2. Press "Add Webhook"
  3. Enter in the url where your app will sit followed by "/git_hook" for instance: http://awesome-company-site.com/git_hook
  4. Generate and enter in Secret (https://developer.github.com/webhooks/securing/). This secret is what you'll set when setting gitHookSecret
  5. Make sure "just push events" is selected.
  6. Press "Add Webhook"

Local Development

Ensure you've set the following environment variables:

$ export NODE_ENV=development
$ export org=your org #(eg. Jam3)
$ export gitToken=your github access token #(details below)

If you're testing webhooks (your server will need to be accessible by github) do the following:

$ export gitHookSecret=your github webhook secret

Optionally you can also do:

$ export repoRegex=regex value

The above will will check which repos licenses will be checked. For instance if the repos you'd like to check started with project- you'd do the following:

$ export repoRegex=project-.+

License

MIT, see LICENSE.md for details.