Pyproject TOML Dependency Extractor

How to use this developer tool

1. Paste the source data or load a local text file.
2. Compare the syntax with the included sample.
3. Select Extract Data or press Ctrl/Command+Enter.
4. Review warnings, then copy or download the result.

What this developer tool does

The result isolates dependency information that is otherwise buried in package-manager syntax. Entry and warning counts help distinguish usable output from records that need manual review.

Treat source URLs, scripts, and package names as untrusted text. This page never executes package content.

Example

The sample input is loaded on first visit. Running it produces a tabular or normalized result that matches the entries visible in the sample.

[project]
name = "demo"
dependencies = ["requests>=2.31", "rich~=13.7"]

[project.optional-dependencies]
dev = ["pytest>=8", "ruff"]

Use cases

• Review a dependency change before committing it.
• Extract a short inventory for an audit ticket.
• Normalize hand-edited package metadata.
• Spot unpinned or conflicting declarations.

Tips for reliable output

• Keep comments when they explain an intentional constraint.
• Validate generated files with the native package manager.
• Do not paste credentials embedded in private source URLs.
• Check prerelease and workspace ranges manually.
• Commit lockfile changes together with the manifest.

Processing details

Processing is local and synchronous. The parser preserves package text where normalization could change its meaning and exposes extracted records through downloadable CSV or JSON when available.

This offline page cannot query registries, resolve dependency graphs, verify checksums, or determine whether a declared version is currently published.