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

@zenstackhq/proxy

v0.5.0

Published

A CLI tool to run an Express server that proxies CRUD requests to a ZenStack backend

Readme

ZenStack Proxy CLI

A CLI tool to run an Express server with ZenStack proxy integration directly from the command line.

Installation

npm install @zenstackhq/proxy

Usage

Start the Server

zenstack-proxy [options]

Options

  • -z, --zenstack <path> Path to ZenStack generated folder
  • -p, --port <number> Port number for the server (default: 8008)
  • -s, --schema <path> - Path to ZModel schema file (default: "schema.zmodel")
  • -d, --datasource-url <url> Datasource URL (overrides schema configuration)
  • --studioAuthKey <key> Authentication key from ZenStack Studio. When set, the proxy will only accept requests signed by your Studio project.
  • -l, --log <level...> Query log levels (e.g., query, info, warn, error)
  • --signature-tolerance-secs <number> Time tolerance in seconds for signed requests (default: 60)

Examples

Basic Usage

Start a server with default settings (searches for ZenStack output automatically):

zenstack-proxy

Specify ZenStack schema and generated output

zenstack-proxy -s ./schema/schema.zmodel -z ./generated/zenstack

Custom Port

zenstack-proxy -p 8888

Enable signed requests

zenstack-proxy --studioAuthKey "MCowBQYDK2VwAyEAFSJV7wjdFuDz2CqYX7hGnITQvcmJYy7OJQq2Cy2Eiqs="

When --studioAuthKey is provided, every incoming request must include an X-ZenStack-Signature header in the format t=<unix timestamp>,v1=<base64url signature>. The signed message format matches ZenStack Studio: payload + timestamp [+ authorizationToken].

  • For GET and DELETE requests, payload is the raw query string without the leading ?.
  • For body-based requests, payload is the exact JSON request body string.
  • For requests without query params or a request body, payload is an empty string.
  • If an Authorization: Bearer <token> header is present, append <token> to the signed message.

Server Endpoints

The server provides the following endpoints:

ZenStack Model API

  • POST /api/model/:model/:operation - All ZenStack operations (find, create, update, delete, etc.)

The ZenStack middleware handles all CRUD operations for your models.

Metadata

  • GET /api/schema - Get complete schema metadata (models + enums)

License

MIT