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

@zalify/cli

v0.1.4

Published

Zalify CLI - command-line interface for Zalify

Readme

@zalify/cli

Zalify CLI – command-line interface for Zalify.

Install

npm i -g zalify
# or
npm i -g @zalify/cli@latest

Usage

zalify version    # Print version and check for updates
zalify -v         # Same as --version (built-in)
zalify --version  # Output current version only

Commands

  • version – Prints Zalify CLI version: x.x.x and, if a newer version exists on npm, suggests running npm i -g @zalify/cli@latest to update.

Development

Requires Bun.

bun install
bun run dev version   # Run CLI from source (TypeScript)
bun run build         # Build to dist/
bun run typecheck     # Type-check only

Publishing

Publishing requires NODE_AUTH_TOKEN. Copy .env.example to .env and set your token (do not commit .env). You can also set NODE_AUTH_TOKEN in your shell.

Release only bumps the version in package.json (no git commit or tag). Commit and tag the version bump yourself if desired. Bun loads .env so NODE_AUTH_TOKEN is available.

bun run release        # Default: patch (x.x.X)
bun run release -- -pa # Patch
bun run release -- -mi # Minor (x.X.0)
bun run release -- -ma # Major (X.0.0)

The release scripts load .env and fail with a clear error if NODE_AUTH_TOKEN is missing.

To allow npm i -g zalify, publish the wrapper package after releasing @zalify/cli: from the repo root run npm publish --access public in the zalify/ folder (it depends on @zalify/cli and exposes the same binary).