Input: TOML
Limit: 1 MiB
Runtime: Browser

Preflight pyproject.toml metadata offline

Apply current PyPA metadata rules after TOML parsing and distinguish field errors from filesystem, backend, tool, and index checks.

Local processingNo sign-upNo content logging

Check pyproject.toml

Inputs are limited to 1 MiB and stay in this browser tab.

Python project preflight

Nothing is placed in a URL, account, or remote log.

Result

Run the tool to see a local result.

What this tool does

Strict, bounded, local processing

This offline preflight validates standardized packaging metadata. It does not import a backend, inspect files, resolve dependencies, verify tool namespaces, build, or upload.

Static and dynamic metadata cannot conflict

Project name is static. Version must be static or dynamic, and no field may be supplied both ways. Dependencies, readme, people, entry points, and licenses have documented types.

Packaging context remains unresolved

Referenced paths, backend import, dynamic metadata, resolution, classifiers, tool ownership, builds, and index acceptance require other systems.

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.Cargo.toml ValidatorLayer documented Cargo manifest rules over TOML syntax and separate definite errors from checks requiring a workspace, filesystem, registry, or compiler.