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

zipup-cli

v0.0.17

Published

zipup cli

Readme

Zipup CLI

Zipup CLI is a command-line tool used to deploy build artifacts to Zipup Cloud. It helps you package your application, apply deployment rules, and securely upload artifacts to the Zipup platform.

👉 Learn more about Zipup Cloud here: zipup cloud

What it does

Zipup CLI handles the full deployment flow:

📦 Builds and packages your application artifact 🚫 Applies ignore rules to exclude unnecessary files 🔐 Signs artifacts for integrity verification ☁️ Uploads the artifact to Zipup Cloud 📊 Does a health check of the deployment

Installation

Install the zipup-cli globally

npm i -g zipup-cli

Usage

zipup deploy --build-folder .

Configuration Sources

Zipup supports three configuration sources:

  • CLI flags (highest priority)
  • Environment variables
  • Config file (zipup.config.json)

Configuration Matrix

| CLI | FILE | ENV | Merge Behavior | Usecase | |----------------|-------------|------------------|--------------------|-------------------------------------------------------------------------------------------------------| | --host | host | ZIPUP_HOST | Replace | Defines zipup admin console url, where deployment request is sent. (like https://admin.zipup.dev) | | --app-key | appKey | ZIPUP_APP_KEY | Replace | Identifies the app for which artifact is being deployed. | | --secret-key | secretKey | ZIPUP_SECRET_KEY | Replace | Signs the deployment artifact for integrity verification on the server. | | --build-folder | buildFolder | - | Replace | Defines the directory to be packaged and deployed as the build artifact. | | --ignore | ignore | - | Merge | Specifies glob patterns for files excluded from the deployment artifact. We use picomatch internally. |

Resolution Rules

  • Replace behavior: Values are resolved with priority CLI > ENV > FILE. For example, if buildFolder is defined in both zipup.config.json and CLI flags, the CLI value takes precedence.
  • Merge behavior: Some fields (e.g., ignore) are merged across sources instead of being replaced.
  • In CI/CD environments, appKey and secretKey should be supplied through environment variables.