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 🙏

© 2026 – Pkg Stats / Ryan Hefner

firebase-provider-stats

v1.0.3

Published

Tiny CLI tool to get provider stats for firebase

Readme

firebase-provider-stats

Tiny nodejs based tool to calculate some quick stats based on Firebase Auth.

Example usage

Why this project?

Because I needed to figure out if my Facebook provider was still worth having in my project or if I could safely just wipe it by looking at the number of users that was registered with Facebook.

Firebase auth is amazing at removing the pain of authentication handling and securing logins. However, when it comes to providing data about who is registered, you need to add some effort yourself.

Usage

First, you need to download your auth data. This is most easily done using the firebase cli:

firebase --project <optional> auth:export users.json

Then you run this little tool to get the data out:

npm install -g firebase-provider-stats
firebase-provider-stats users.json

Details about the stats

This tool is at the mercy of what data the firebase user export provides. This means, email and phone registrations cannot be easily detected as these simply get added as data to the user object rather than as providers.

In order to count the email and phone logins, the existance of these fields are compared. Email is registered for any provider that is added with email as well, so I consider it a user with email login only if no providers are given.

⚠️ For Apple ids, we do not get the provider details in the json so we have to rely on checking if the registered email is an appleid.com relay email. This is not a perfect solution but it's the best we can do for now.

Build

To install dependencies and run locally:

npm install
npm link
firebase-provider-stats <your-file>

And to test:

npm test

This will use the provided example testfile example.json.

Publishing

Publishing to NPM is done automatically by any tag.

  1. Update version in package.json
  2. Tag it with git tag vx.x.x and git push origin vx.x.x
  3. Sit back and let it build

Credits

Big shoutout to LogRockets article on creating CLI tools

License

The MIT License (MIT)