Manifest rules begin after TOML
The preflight checks package names, editions, Rust-version shape, documented field types, dependency source combinations, feature references, targets, and workspace structure.
- Input
- TOML
- Limit
- 1 MiB
- Runtime
- Browser
Preflight a Cargo.toml manifest offline
Layer documented Cargo manifest rules over TOML syntax and separate definite errors from checks requiring a workspace, filesystem, registry, or compiler.
Local processingNo sign-upNo content logging
Check Cargo.toml
Inputs are limited to 1 MiB and stay in this browser tab.
Cargo manifest preflight
Nothing is placed in a URL, account, or remote log.
What this tool does
Strict, bounded, local processing
This is an offline structural preflight, not cargo check. It cannot prove that targets exist, inheritance resolves, dependencies download, code compiles, or publication succeeds.
Unresolved checks stay visible
Paths, member globs, inherited values, registries, Git references, compiler compatibility, and publication policy require context this operation never reads.
Primary references
Questions and answers
Related TOML tools
TOML ValidatorParse TOML strictly and report safe diagnostics and structural facts without formatting or applying an application manifest contract.TOML Schema ValidatorParse TOML, project supported values into a documented schema model, and return structured violations from a supplied JSON Schema.pyproject.toml ValidatorApply current PyPA metadata rules after TOML parsing and distinguish field errors from filesystem, backend, tool, and index checks.