depvex
depvex generates and checks requirements.txt files from static Python
imports. It is designed for a single Python application and for repositories
that contain multiple independently managed services.
Core capabilities
- AST-based detection of
importandfrom ... import ...statements. - Standard-library filtering and per-import opt-out with
# ignore depvex. - Skips imports inside
if TYPE_CHECKING:blocks to avoid adding type-only imports. - Recursive discovery across
.pyand Jupyter Notebook (.ipynb) files. - Automatically isolates notebook dependencies into
requirements-notebooks.txt(or merges intorequirements.txtvianotebooks_target). - Built-in directory exclusions plus YAML
ignore_dirsandignore_packagessupport. - Import-module to installed-distribution mapping through
importlib.metadata. - Version lookup from installed metadata without subprocesses, followed by an optional PyPI fallback.
- Existing dependency pins are retained when the package remains in use; stale entries are removed during a scan.
- One-time scan, CI-oriented check, and debounced filesystem watch mode.
- Per-service requirements files plus a root requirements file for microservice repositories.
- Detailed check output for missing, stale, and changed entries.
- Optional
[project].dependenciessync/check and service dependency reports. - Compatibility analysis for one package or an entire requirements-style file.
Install
Requires Python 3.11+.
python -m pip install depvex
Install PyYAML separately to enable depvex.yaml or depvex.yml:
python -m pip install PyYAML
Intended command interface
depvex --scan .
depvex --check .
depvex --watch .
depvex --report .
--scanupdates requirements files.--checkreturns exit code0when requirements files match the detected imports and1otherwise.--watchperforms an initial scan and updates files after created or modified Python-file events.--reportprints dependencies per service and shared dependencies without changing files.- Multiple commands can be selected together, for example
depvex --scan --check --report .; they run sequentially by default. - Use
--paralleland optionally--jobs Nto run one command concurrently across independent project paths, for exampledepvex --parallel --scan ./service-a ./service-b. Use--continue-on-errorto continue sequential execution after a failed command. - Do not combine
--parallelwith multiple commands on the same path; commands such asscanandcheckdepend on one another and must run sequentially. - Use
--ignore-dir DIRto add a directory exclusion from the CLI. Repeat the option for multiple directories; CLI exclusions are combined with YAMLignore_dirsvalues. --watchcannot be combined with other commands because it is long-running.
Use --pyproject with --scan to write, or with --check to verify,
[project].dependencies in an existing pyproject.toml.
Compatibility analysis
Check a package before installing it, including its direct and transitive dependencies:
depvex --compatibility "fastapi>=0.115" .
depvex --compatibility "fastapi>=0.115" --format json .
To check every requirement in a requirements-style file, use
--compatibility-file:
depvex --compatibility-file requirements.txt .
depvex --compatibility-file install.txt --format json .
Blank lines and comments are ignored, as are -r, --, -e, and git+
entries. The analyzer checks each remaining requirement against the project's
existing requirements without installing packages or modifying files.
This is more than an installed-package check. pip show PACKAGE tells you
which version is installed in the current environment; Depvex checks whether
the version you request satisfies the project's declared constraints. For
example, if requirements.txt contains requests==2.34.2, checking
requests==2.34.1 correctly reports a conflict, even if requests is already
installed, because the exact version pin is not satisfied.
The analyzer also follows direct and transitive dependencies. A package can have no direct conflict while one of its dependencies conflicts with a package already pinned by the project. This makes the command useful as a pre-install review before modifying the environment or committing a new requirements file.
By default, package metadata may be resolved from PyPI. Add --no-network to
use only locally installed metadata. A confirmed conflict returns exit code
1, an uncertain result returns 2, and 0 means all checked requirements
are compatible.
Version note
The new source interface above is not compatible with older published
releases, which use positional commands such as depvex check .. Install and
invoke one version consistently in CI.
Single application
Without configured services, scanning a directory creates or updates its
single requirements.txt:
depvex --scan ./my-app
Microservices
Define direct child service folders in depvex.yaml:
micro_servi_folders:
- api
- worker
ignore_dirs:
- tests
ignore_packages:
- pytest
- depvex
Scanning the repository produces:
repository/
├── api/requirements.txt
├── worker/requirements.txt
└── requirements.txt
The root file covers Python files outside api and worker; service-only
imports are excluded from it. Watch mode rescans only the affected service
when a file changes below a configured service folder.
The current key spelling is micro_servi_folders, and service configuration is
read from YAML only. config.json is used for CAPTIVE_PORTAL_URLS and
debounce_seconds, not service discovery.
CI
Install the target project's dependencies and the checked-out project before checking, so package metadata is available and the local code is executed:
- run: |
python -m pip install -r requirements.txt
python -m pip install .
- run: depvex --check .
check reports missing, stale, and changed dependency entries. Run scan,
review the resulting diff, and commit expected changes.
Scope and roadmap
Depvex does not resolve dynamic imports or replace a lockfile manager. Future work includes a canonical microservice configuration key and broader automated coverage for single-project, microservice, watch, and CI scenarios.
Metadata
Release files for depvex 0.1.11
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| depvex-0.1.11.tar.gz | 371.9 kB | Without provenance | Details for depvex-0.1.11.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| depvex-0.1.11-py3-none-any.whl | Python 3 | none | any | Details for depvex-0.1.11-py3-none-any.whl |
Total release size: 541.4 kB
Release files / depvex-0.1.11.tar.gz
| Download URL | depvex-0.1.11.tar.gz |
|---|---|
| Size | 371.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
83b243d1c67de84f9474fcd8d70b600c055eee733dd015f11b8cae89b147e022
|
|
BLAKE2b-256 checksum How to use checksums |
76b6a01c553c246a8844f08e2a2cd30a2a1f729b8273fba98118e2a22c0fabfa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.17
|
Release files / depvex-0.1.11-py3-none-any.whl
| Download URL | depvex-0.1.11-py3-none-any.whl |
|---|---|
| Size | 169.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5c5237cd9ff5033b4af9a9aa9993f3ad54bf0164edaa11f4e651c37a226cb9e7
|
|
BLAKE2b-256 checksum How to use checksums |
328ce7ebcf9ffbdfff8ea0a67a3425e17242eb9ef0fd5fd56a323646fdc0227d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.17
|
Security for depvex 0.1.11
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.