Proto Wire Break Check
Runs the same checker as our npm package on a Node.js runtime that pip installs for you (
nodejs-wheel-binaries) - no system Node.js needed. Your files are checked locally.
Names the .proto edits that keep compiling and quietly change what old gRPC readers see
Install
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.
--ruleslists 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.
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": "proto-wire-break-check", "args": ["--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: pip install rulestamp-proto-wire-break-check && proto-wire-break-check --dir . --ci
The folder sweep, reports and CI mode need one licence — one payment, no subscription. Set READYSTACK_LICENSE=<key> or run --license <key> once.
Install (PyPI)
pip install rulestamp-proto-wire-break-check
proto-wire-break-check --help
Metadata
Release files for rulestamp-proto-wire-break-check 1.0.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| rulestamp_proto_wire_break_check-1.0.7.tar.gz | 18.8 kB | Without provenance | Details for rulestamp_proto_wire_break_check-1.0.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_proto_wire_break_check-1.0.7-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_proto_wire_break_check-1.0.7-py3-none-any.whl |
Total release size: 39.9 kB
Release files / rulestamp_proto_wire_break_check-1.0.7.tar.gz
| Download URL | rulestamp_proto_wire_break_check-1.0.7.tar.gz |
|---|---|
| Size | 18.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
20faa93fc6e4ea3ba10dd9395af8c9b218afe411124670ae296649ef8f0f48f1
|
|
BLAKE2b-256 checksum How to use checksums |
a626de8e2568cba92831709e00ae15113df90dc0dd84c212055fd04d12ea6e10
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / rulestamp_proto_wire_break_check-1.0.7-py3-none-any.whl
| Download URL | rulestamp_proto_wire_break_check-1.0.7-py3-none-any.whl |
|---|---|
| Size | 21.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e0950218471d40bd2711cb837399a2ea02441471853ae1fd11d7b5d9dae501e1
|
|
BLAKE2b-256 checksum How to use checksums |
ae6e324324986082bbf9c81dcffae6781e93708ed123508528e023343967bdc2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for rulestamp-proto-wire-break-check 1.0.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.