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

cardinal-bot

v1.6.0

Published

<div align="center">

Readme

Cardinal Bot

Code Factor GitHub stars GitHub issues Continuous Integration

Table of Contents

Invite Cardinal to your server Click here

Beta Testing for Cardinal

If you want to be a beta tester you can join the support server and create a ticket to become a beta tester. Keep in mind that you might not be accepted since we dont usually need that many beta testers.

Developing on Cardinal

Requirements

You should have a good understanding of the following:

Contributing

To contribute to this repository, feel free to fork the repository and make your own changes. Once you have made your changes, you can submit a pull request.

  1. Fork the repository and select the main branch.
  2. Create a new branch and make your changes.
  3. Make sure you use a proper linter and a code formatter. [^lint]
  4. Make sure you have a good commit message.[^commit]
  5. Push your changes.
  6. Submit a pull request here.

[^env]: You will need to create a .env file in the root directory of the project. [^lint]: We recommend using eslint and prettier to lint your code. [^commit]: We strongly follow the Commit Message Conventions. This is important when commiting your code for a PR.