Cargo.toml Publish Gate - crates.io
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 every crates.io publish blocker in a Cargo.toml before the upload burns a version number.
Install
cargo-publish-gate file
Node 18+. The same 13 rules as the VS Code extension, from a terminal or CI.
Free
- Open any Cargo.toml, run the check, and read every crates.io publish blocker in it with its line number and its fix - nothing hidden, no countdown, no watermark.
--ruleslists every rule
With a licence ($29 once)
- Gates every Cargo.toml in the workspace in one pass and writes a dated pre-publish report file you keep and attach to the release pull request.
cargo-publish-gate --dir ./templates --report html --out report.html
A contract Rust engineer on the open freelance market starts near $50 an hour, and the hand check of one release manifest against the crates.io rules takes most of that hour, at every release.
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "cargo-publish-gate": { "command": "cargo-publish-gate", "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: Cargo.toml Publish Gate - crates.io
run: pip install rulestamp-cargo-publish-gate && cargo-publish-gate --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-cargo-publish-gate
cargo-publish-gate --help
Metadata
Release files for rulestamp-cargo-publish-gate 1.0.5
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_cargo_publish_gate-1.0.5.tar.gz | 15.9 kB | Without provenance | Details for rulestamp_cargo_publish_gate-1.0.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_cargo_publish_gate-1.0.5-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_cargo_publish_gate-1.0.5-py3-none-any.whl |
Total release size: 33.8 kB
Release files / rulestamp_cargo_publish_gate-1.0.5.tar.gz
| Download URL | rulestamp_cargo_publish_gate-1.0.5.tar.gz |
|---|---|
| Size | 15.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3d0baaa870710e119e1caeddb3442046e5494630fbffc7054b17e193de0126d2
|
|
BLAKE2b-256 checksum How to use checksums |
7518f33458bf02814ad7174b722ff33a4439568a905f5787604a43fc684151e2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / rulestamp_cargo_publish_gate-1.0.5-py3-none-any.whl
| Download URL | rulestamp_cargo_publish_gate-1.0.5-py3-none-any.whl |
|---|---|
| Size | 17.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fc08995db32f08753c46b59eb572e99b64804dcd3f3147513841edb49358803a
|
|
BLAKE2b-256 checksum How to use checksums |
b04927479de54f83f931debed07ad4fc9a492b26b39df351d3f194a2cefc39c5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for rulestamp-cargo-publish-gate 1.0.5
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.