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

police

v0.6.0

Published

policing tool for dependency package versions

Readme

police

A module dependency version policing tool. It goes through all your repositories on github which has package.json. Then it analyzes the dependencies and reports back to you about all the outdated packages.

It also can suggest corrections to your package.json file in certain cases.

Running

Installation

Install police globally from npm registry by typing the following command

npm install police -g

Usage

For the first time after you installed police, you need to authenticate yourself to github. This is a one-time step

police auth

Note: We will not save your github password anywhere. A token which we acquire during the authentication will be used thereafter. And it will be saved in a file with permissions 0600

Does not work when 2 factor authorization is enabled. Please create a personal use token here and edit the ./policeconf file.

# To police your module dependencies
police

# To police a particular module (You should give the repository name)
police octonode

# To police another user/org module dependencies
police -u flatiron

# To police a particular module of another user/org (You should give the repository name)
police flatiron/plates

# To police a local module or package.json file
police -l ~/octonode
police -l ~/octonode/package.json

# To continue checking even though errors are encountered (Doesnt work with -l)
police -f
police -u flatiron -f

# To edit all the fields in package.json (Doesnt work with -l)
police -e

# To add the missing fields to package.json (Doesnt work with -l)
police -a

# To update dependencies in package.json
police -t

Given below are some ideal commands to help you.

# An ideal police command for github user for the first time on a module
police -f -e -t

# An ideal police command for github user
police -f -a -t

# An ideal police command locally
police -l ~/octonode -t

The token which we acquied during auth will be stored in $HOME/.policeconf. If you want to use another config file

police octonode --conf /etc/policeconf
police octonode --conf ~/.conf

If you want to destory your token, you can use

police -d
police --destroy

Calling police with help option will display all the above

police -h
police --help

Help

If you like this project, please watch this and follow me.

Testing

npm test

Contributors

Here is a list of Contributors

TODO

  • Option to isolate dependency checking and suggestions
  • Support multiple npm registries (custom)
  • Display progress bar instead of listing the dependencies (use charm)
  • Caching package.json blobs per commit
  • Start using octonode module
  • Command for setting and deleting configurations

I accept pull requests and guarantee a reply back within a day

License

MIT/X11

Bug Reports

Report here. Guaranteed reply within a day.

Contact

Pavan Kumar Sunkara ([email protected])

Follow me on github, twitter

Concept by: Martin Wawrusch ([email protected])