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

warda-cli

v1.0.2

Published

Warda CLI utility

Readme

Installation

NPM install

First of all, install warda-cli library:

npm i -g warda-cli

Basic config setup

After installation, you should set basic configuration:

wrd init --baseURL=[BASE_URL] --apiKey=[API_KEY]

Git templates setup

Option 1 (no git template dir atm or global post-commit hook)

If you don't have git template dir yet, or you have one, but don't have post-commit hook in there, just run:

wrd init-hooks -g

During this, there will be created ~/.git-templates folder, where your git-hooks will be stored.

Option 2

If previous option has failed for you, it means you already have git templates dir and you have default post-commit hook, and you'll need manually add following line to its end:

wrd post-commit

After global hook setup

You'll need to run

git init

in all repos, in which you want to use that hook.

Important!

It's not necessary: you may init post-commit hook individually for any repo you want using wrd init-hooks # or ih w/o -g flag.

Login

Using the tool requires you to have an account, so just:

wrd login

and follow the instructions.

API

init-hooks (alias ih)

Adds post-commit hook to the current git repo.

last

This command allows you to send for review previous commit OR staged changes if you have any (you'll be asked what exactly you want to send).

diff <GIT_DIFF_PARAMS>

Sends diff got by running git diff <GIT_DIFF_PARAMS>. Doesn't require init-hooks before.