Skip to main content

pip-check-resolve

pip-check-resolve inspects an installed Python environment without changing it. It finds missing or incompatible dependencies and traces each problem back to the likely top-level packages that caused it.

Unlike a resolver, it answers why the environment that exists now is broken. It does not install packages, try alternative versions, or contact PyPI.

Usage

Run inside the environment to inspect the current interpreter:

$ pip-check-resolve

Or keep the tool isolated and point it at another environment:

$ uvx --from pip-check-resolve pip-check-resolve --python .venv/bin/python

Machine-readable output and expanded causal paths are available:

$ pip-check-resolve --python .venv/bin/python --format json
$ pip-check-resolve --all-paths --max-paths 100

Exit status is 0 for a consistent environment, 1 when package or metadata issues are found, and 2 when the target interpreter cannot be inspected.

What is checked

  • missing dependencies;
  • versions that do not satisfy their declared requirements;
  • incompatible Requires-Python metadata;
  • duplicate normalized distribution names;
  • malformed package requirements or metadata.

Roots are identified from a distribution's REQUESTED marker when available and otherwise inferred from the installed dependency graph. Python packaging does not reliably preserve which extras were requested, so requirements conditional on extra are skipped and the report records that limitation.

Releasing

Releases are published from GitHub tags using PyPI Trusted Publishing. The tag must be the project version prefixed with v, for example v0.1.0. Update the version in both pyproject.toml and src/pip_check_resolve/__init__.py, commit, and then create and push the matching tag:

$ git tag v0.1.0
$ git push origin v0.1.0

The publish.yml workflow tests the package, builds and checks its wheel and source distribution, and publishes them to PyPI using short-lived OIDC credentials. The PyPI Trusted Publisher must use owner matplo, repository pip-check-resolve, workflow publish.yml, and environment pypi.

Metadata

Release files for pip-check-resolve 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pip-check-resolve 0.1.0
File Size Uploaded Provenance
pip_check_resolve-0.1.0.tar.gz 12.3 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for pip-check-resolve 0.1.0
File Interpreter ABI Platform
pip_check_resolve-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 22.8 kB

Release files / pip_check_resolve-0.1.0.tar.gz

Download URL pip_check_resolve-0.1.0.tar.gz
Size 12.3 kB
Tags Source
SHA-256 checksum
How to use checksums
d648cb77e98425aeafa1e34209c58c6adad7668c69119bb1b9189cee9079540a
BLAKE2b-256 checksum
How to use checksums
50e953b38829470becf2c84d914878ba63b50be422b2ad5cd4bffc219307c2a1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 13, 2026.

Transparency log

Release files / pip_check_resolve-0.1.0-py3-none-any.whl

Download URL pip_check_resolve-0.1.0-py3-none-any.whl
Size 10.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
88852e53b9f249dda0b2da607f9564411d3915bfb23398b49ae2c6826016e0be
BLAKE2b-256 checksum
How to use checksums
349eeb7693212b84cb9e9ec89a0c3a4a42ebcb56b7f7a6045d8dee956f7a7193
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 13, 2026.

Transparency log

Security for pip-check-resolve 0.1.0

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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for pip_check_resolve-0.1.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 13, 2026.

Transparency log

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.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page