pip-check-reqs
Find packages that should or should not be in requirements for a project
Decision gist · record as of 2026-08-14
Yes. This is a stable, actively maintained linter that solves a real problem—keeping requirements.txt in sync with actual code. Low install friction, no security issues, and MIT-licensed. Worth adding to any Python project's CI pipeline, especially if you want to avoid the surprise of discovering you've been relying on a transitive dependency.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.10 or later; project must have a requirements.txt or pyproject.toml file to check against.
- Low friction install with only two stable runtime dependencies (packaging and pip).
- Active maintenance with a recent release 15 days ago and consistent commits.
License · maintenance · safety
permissive license (permissive) — MIT license is permissive; you can use, modify, and distribute this package freely with minimal restrictions.
last release 2026-07-30 (15 days) · last repo commit 2026-08-13 · 135 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 87,980 downloads/mo, #13,758 on PyPI
Alternatives
Verify before relying
pip install pip-check-reqs
# In your project directory:
pip-missing-reqs --ignore-file=tests/* myproject
pip-extra-reqs --ignore-file=tests/* myproject- Whether the tool correctly handles all edge cases in conditional imports and dynamic dependency inclusion.
- Performance characteristics when analyzing very large codebases with thousands of modules.
What it is and what it does
pip-check-reqs is a linter that compares your project's actual code imports against your declared dependencies. It runs two checks: pip-missing-reqs finds modules you're importing that aren't listed in requirements.txt (catching transitive dependencies you've accidentally relied on), and pip-extra-reqs finds packages in requirements.txt that your code never imports (identifying dead weight). The tool supports excluding test files and conditionally-imported modules via command-line flags, and can work with either requirements.txt or pyproject.toml.
You run it as a command-line tool in your project directory, pointing it at your source code. It parses all imports, maps them to their package names using packaging metadata, and reports mismatches. It's designed to integrate into CI/CD via tox or similar test runners, letting you catch dependency drift before it causes production surprises.
Use it for
- Detect transitive dependencies you've accidentally relied on so you can add them explicitly to requirements.txt.
- Find and remove unused packages from requirements.txt to reduce your dependency footprint and attack surface.
- Validate that a refactored codebase still has all the dependencies it needs after removing old code.
- Integrate into CI to prevent dependency drift—catching missing or extra packages before they reach production.
- Audit legacy projects to understand which declared dependencies are actually used versus which are cruft.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes.
This is a stable, actively maintained linter that solves a real problem—keeping requirements.txt in sync with actual code. Low install friction, no security issues, and MIT-licensed. Worth adding to any Python project's CI pipeline, especially if you want to avoid the surprise of discovering you've been relying on a transitive dependency.
Install
pip-check-reqs on PyPI
Before you install
Low friction install with only two stable runtime dependencies (packaging and pip). Active maintenance with a recent release 15 days ago and consistent commits.
Requires Python 3.10 or later; project must have a requirements.txt or pyproject.toml file to check against.
License in practice
MIT license is permissive; you can use, modify, and distribute this package freely with minimal restrictions.
Quickstart
pip install pip-check-reqs
# In your project directory:
pip-missing-reqs --ignore-file=tests/* myproject
pip-extra-reqs --ignore-file=tests/* myprojectVerify before relying
- Whether the tool correctly handles all edge cases in conditional imports and dynamic dependency inclusion.
- Performance characteristics when analyzing very large codebases with thousands of modules.
Package facts
| License | permissive license permissive |
| Python support | Supports the current Python release >=3.10 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 2 packagespackagingpip |
| Maintenance | Actively maintained 15 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 87,980 / month, #13,758 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 LicenseOperating System :: Microsoft :: WindowsOperating System :: POSIXProgramming Language :: Python :: 3 :: OnlyProgramming Language :: Python :: 3.10Programming Language :: Python :: 3.11Programming Language :: Python :: 3.12Programming Language :: Python :: 3.13Programming Language :: Python :: 3.14Topic :: Software Development :: Build Tools |
Evidence: pip_check_reqs-3.0.0-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 › “audit requirements.txt”
- pip-check-reqsAudits Python project imports against requirements.txt to find…
- liccheckScans Python project dependencies in requirements.txt or…
- uv-secureScans uv.lock, pylock.toml, and requirements.txt files for known…
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 creosote · fawltydeps · flake8-requirements · deptry · pipreqs-fivetran · update_checker · requirements-detector · depgather · pipreqs · liccheck