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

@readystack/proto-wire-break-check

v1.0.6

Published

Names the .proto edits that keep compiling and quietly change what old gRPC readers see

Readme

Proto Wire Break Check

Protobuf Breaking Change Lint - wire compatibility (.proto) — finds the line

Names the .proto edits that keep compiling and quietly change what old gRPC readers see

Install

npx @readystack/proto-wire-break-check file

Node 18+. The same 17 rules as the VS Code extension, from a terminal or CI.

Free

  • Open any .proto, run one command, and all 17 rules run on that file: every finding with its line number, what an old reader will do with that byte, and the edit that keeps the wire intact. The 27-line sample in the repo returns 18 findings, 10 of them errors; the clean sample returns 0. No key, no account - that is the whole job for one file.
  • --rules lists every rule

With a licence ($29 once)

  • The full version sweeps every .proto in the workspace in one pass and writes PROTO-WIRE-AUDIT.md plus audit.json - one file you can commit, attach to a pull request, or fail a build on. $29 once, one licence key per person or team seat.
@readystack/proto-wire-break-check --dir ./templates --report html --out report.html

A contract backend engineer runs $60+/hour on the public marketplaces, and reviewing one service's schema history by hand is an afternoon of that.

Use from an AI agent (MCP)

Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:

{ "mcpServers": { "proto-wire-break-check": { "command": "npx", "args": ["-y", "@readystack/proto-wire-break-check", "--mcp"] } } }

Tools: check_text and check_file (free) · check_dir (licence). The agent gets every finding with the line number.

Use in CI

- name: Proto Wire Break Check
  run: npx -y @readystack/proto-wire-break-check --dir . --ci

(container: docker run --rm -v "$PWD:/work" getreadystack/proto-wire-break-check --dir /work --ci)

The folder sweep, reports and CI mode need one licence — one payment, no subscription. Set READYSTACK_LICENSE=<key> or run --license <key> once.

Get a licence