dparse
A parser for Python dependency files
Decision gist · record as of 2026-08-14
Yes, if you need to parse Python dependency files programmatically. The package is stable, has low install friction, carries a permissive license, and has no known vulnerabilities. However, be aware that maintenance is dormant (644 days since last release)—it is suitable for stable, read-heavy use cases but may not receive updates for new Python versions or emerging dependency file formats.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.7 or later; Python 2.7 is not supported.
- Low install friction with only two runtime dependencies (packaging and tomli).
- Maintenance is dormant—last release was 644 days ago and the repository shows no recent activity, though it remains archived=false and the package is marked Production/Stable.
License · maintenance · safety
MIT license (permissive) — MIT license (permissive) means you can use, modify, and distribute this package freely with minimal restrictions, making it safe for both open-source and commercial projects.
last release 2024-11-08 (644 days) · last repo commit 2024-11-25 · 64 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 4,712,718 downloads/mo, #2,248 on PyPI
Alternatives
Verify before relying
from dparse import parse, filetypes
content = "South==1.0.1\npycrypto>=2.6"
df = parse(content, file_type=filetypes.requirements_txt)
print(df.json())- Whether dormant maintenance (644 days since last release) poses a risk for future Python version compatibility or dependency updates.
- Completeness of parsing for edge cases in supported file formats, particularly conda.yml and Pipfile with complex configurations.
What it is and what it does
dparse is a lightweight parser that reads Python dependency declaration files and extracts their contents into a structured, queryable format. It supports a range of common dependency file types—requirements.txt, conda.yml, tox.ini, Pipfile, Pipfile.lock, poetry.lock, and pyproject.toml—though not all support both parsing and updating. The package returns dependency metadata as JSON-serializable objects, including package names, version specifications, hashes, and source information.
You would use dparse when you need to programmatically analyze or manipulate Python dependency files—for example, in a dependency auditing tool, a lock-file validator, or a build system that needs to read and understand what packages a project declares. It handles the parsing complexity so you can work with clean Python objects instead of raw file text.
Use it for
- Audit Python projects by parsing their dependency files to extract and analyze all declared packages and versions.
- Build a dependency update tool that reads requirements.txt or Pipfile and rewrites them with updated versions.
- Validate lock files (Pipfile.lock, poetry.lock) by parsing them to check for consistency or security issues.
- Integrate dependency parsing into a CI/CD pipeline to extract and report on project dependencies.
- Create a multi-format dependency analyzer that can read conda.yml, tox.ini, and requirements.txt from the same codebase.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you need to parse Python dependency files programmatically.
The package is stable, has low install friction, carries a permissive license, and has no known vulnerabilities. However, be aware that maintenance is dormant (644 days since last release)—it is suitable for stable, read-heavy use cases but may not receive updates for new Python versions or emerging dependency file formats.
Install
dparse on PyPI
Before you install
Low install friction with only two runtime dependencies (packaging and tomli). Maintenance is dormant—last release was 644 days ago and the repository shows no recent activity, though it remains archived=false and the package is marked Production/Stable.
Requires Python 3.7 or later; Python 2.7 is not supported.
License in practice
MIT license (permissive) means you can use, modify, and distribute this package freely with minimal restrictions, making it safe for both open-source and commercial projects.
Quickstart
from dparse import parse, filetypes
content = "South==1.0.1\npycrypto>=2.6"
df = parse(content, file_type=filetypes.requirements_txt)
print(df.json())Verify before relying
- Whether dormant maintenance (644 days since last release) poses a risk for future Python version compatibility or dependency updates.
- Completeness of parsing for edge cases in supported file formats, particularly conda.yml and Pipfile with complex configurations.
Package facts
| License | MIT license permissive |
| Python support | Supports the current Python release >=3.7 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 2 packagespackagingtomli |
| Maintenance | Dormant 644 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 4,712,718 / month, #2,248 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Development Status :: 5 - Production/StableIntended Audience :: DevelopersLicense :: OSI Approved :: MIT LicenseNatural Language :: EnglishProgramming Language :: Python :: 3Programming Language :: Python :: 3.10Programming Language :: Python :: 3.11Programming Language :: Python :: 3.12Programming Language :: Python :: 3.7Programming Language :: Python :: 3.8Programming Language :: Python :: 3.9 |
Evidence: dparse-0.6.4-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “parse requirements.txt”
- dparseParses Python dependency files (requirements.txt, conda.yml, tox.ini,…
- requirements-parserParses pip requirement files into structured data, extracting package…
- depgatherExtracts and lists dependencies from multiple Python project file…
Give your agent the search over MCP, or paste the wish link into any chat.
More Build Tools packages
Provides reusable utilities for Python packaging interoperability, including version handling, specifiers, markers, requirements, tags, and metadata parsing according to standards like PEP 440 and PEP 425.
Wraps any iterable to display a real-time progress bar in the terminal or Jupyter notebook, showing iteration count, elapsed time, and estimated time remaining.
pip is the standard installer for Python packages, enabling you to download and install packages from the Python Package Index and other indexes into your Python environment.
Hatchling is a standards-compliant Python build backend that handles packaging, metadata, and distribution of Python projects when configured in a project's pyproject.toml file.
Generates Python gRPC service stubs and message classes from Protocol Buffer definitions, enabling developers to build gRPC clients and servers.
pre-commit is a framework for installing and running git hooks written in any language before commits are made, automating code quality and validation checks across multi-language projects.
Install it if your team needs consistent, automated validation at commit time.
See also dparse2 · requirements-detector · pip-requirements-parser · pipfile · plette · requirementslib · pip-upgrader · pip-tools · hashin · docker-image-py