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

pkgchk

v0.1.1

Published

organization-wide package usage comparison

Downloads

4

Readme

pkgchk

organization-wide package usage comparison

oclif Version Downloads/week License

This is a command line tool that will search an entire Github organization for a certain npm dependency. Any repository within the organization that depends on the package in question will be listed along with the version it is currently using so it can be compared to the most recent version available.

Usage

First, you'll need a Github access token. Any token that works with the Github REST API will do. You can start with a simple personal access token.

npm install -g pkgchk
pkgchk --help

Pass this access token in via the token flag or the GITHUB_TOKEN environment variable.

pkgchk [PACKAGE_NAME] -o [ORG_NAME] -t [ACCESS_TOKEN]
GITHUB_TOKEN=[ACCESS_TOKEN] pkgchk [PACKAGE_NAME] -o [ORG_NAME]
PKGCHK_ORG=[ORG_NAME] pkgchk [PACKAGE_NAME] -t [ACCESS_TOKEN]

Examples

pkgchk ember-source -o showbie
pkgchk ember-source -o emberjs
DEBUG=* pkgchk ember-source -o intercom
DEBUG=* pkgchk ember-data -o simplabs

Future Development

  • cache responses from Github API
  • support for npm/yarn lockfiles
  • support other tech stacks and package managers