Cargo.toml Publish Gate - crates.io

Reads Cargo.toml and lists every crates.io publish blocker before you run cargo publish - the version number you burn cannot be re-uploaded. Runs entirely in your browser — nothing is uploaded.

Same engine as the VS Code extension, byte for byte.

Install free

Free for the file open in your editor - no key, no limit. The workspace sweep and the report ask for a key.

Open VSX (Cursor, VSCodium)npmDocker Hub
npx @readystack/cargo-publish-gate <file>
docker run --rm -v "$PWD:/w" getreadystack/cargo-publish-gate /w

Team? One key for every ReadyStack linter, 5 seats, $149 once

Get one email when this rule changes
We watch the regulation and vendor sources behind Cargo.toml Publish Gate - crates.io every day. When a rule changes, you get a single email with what changed and the updated check. No newsletter.

Get the complete version $29

This page is the working piece. The full pack has everything below.

Names every crates.io publish blocker in a Cargo.toml before the upload burns a version number.

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.

Buy the full version — $29

Questions people ask

What does Cargo.toml Publish Gate actually do?

It reads a Cargo.toml manifest and applies 13 rules that crates.io and cargo publish enforce at upload time: missing description or licence, wildcard and git dependencies, path dependencies without a version, the five-keyword and five-category limits, publish = false, a missing repository or readme, and a 2015 or absent edition. Each finding carries its line number and its fix.

Who is this for?

Rust crate authors and release engineers who publish to crates.io: maintainers cutting a release from a workspace, teams whose first upload of a new crate has to land correctly, and anyone whose Cargo.toml was partly written by an AI assistant that filled in dependencies but left description, licence and version placeholders untouched.

Why is a free tool not enough here?

cargo check, cargo build and clippy all compile fine with a wildcard dependency, no licence and no description, because those are registry rules rather than compiler rules. cargo publish is where they appear, and by then the run is live. This gate applies the registry rules offline, in the editor, before the upload.

What is free and what needs the licence key?

Free covers one file completely: open any Cargo.toml, run the check, and read every blocker with its line and its fix. Nothing is hidden, watermarked or limited by a countdown. The licence key adds scope and ownership: every Cargo.toml in the workspace in one pass, plus a dated report file you keep and attach to the release pull request.

What would this cost done by hand?

A contract Rust engineer on the open freelance market starts near $50 an hour, and re-reading the crates.io manifest rules against a release manifest takes most of that hour, once per release. The paid layer is $29 once, with one licence key per person or team seat and a 7-day full refund.

Ask about this tool

One question, answered by the person who built it. Your email only if you want the answer sent.

ENDEJAESPT

Find a tool