---
id: to-requirements-txt
version: "2.0.14"
license: MIT
license_treatment: permissive
maintenance: aging
---

# to-requirements.txt — Automatically add and delete modules to requirements.txt installing them using pip.

License: permissive · Maintenance: aging · Downloads: 214.6K/mo

## What it is and what it does

to-requirements-txt wraps pip to automatically keep your requirements.txt in sync with installed packages. When you install, upgrade, or uninstall a package via pip, the tool updates requirements.txt without requiring manual intervention. It's designed for developers who want their dependency file to always reflect the current environment state.

The package works by hooking into pip's workflow and is configured per project via a simple init command. It supports customization (e.g., limiting to Git repositories, toggling auto-creation of requirements.txt) and integrates into your shell via aliases for sourced execution, which allows it to manage virtual environment activation. After setup, you use pip as normal—the synchronization happens transparently.

Use it for:

- Keep requirements.txt automatically updated when developing in a virtual environment without manual tracking.
- Set up a new project's dependency management in one command (rex init) with automatic venv creation.
- Ensure requirements.txt stays consistent across team members by syncing with every pip operation.
- Reduce merge conflicts in version control by eliminating manual requirements.txt edits.
- Quickly initialize a VirtualEnv-based project with pre-configured dependency tracking.

## Worth the install?

AI-flagged interpretation of the facts above — verify before relying.

Automatically synchronizes your project's requirements.txt with packages you install via pip, keeping dependencies up-to-date without manual editing.

Yes, if you work in Unix environments and want hands-off requirements.txt synchronization. The low install friction, permissive license, and Production/Stable status make it a reasonable choice for developers tired of manual dependency file updates. However, the aging maintenance (468 days since last release) means you should verify it works reliably with your current Python and pip versions before committing to it in a critical project.

## Install

pip install to-requirements-txt
uv add to-requirements-txt
poetry add to-requirements-txt

## Installing to-requirements.txt

Before you install: Low friction install with three lightweight runtime dependencies (appdata, click, colored). Maintenance status is aging—last release was 468 days ago, though the repository remains active and the package is marked Production/Stable.

License in practice: MIT license is permissive; you can use, modify, and distribute this package freely with minimal restrictions.

Quickstart:

pip install to-requirements-txt
rex init
# Then use pip normally; requirements.txt updates automatically

Shell integration requires adding aliases to .bashrc, .zshrc, or equivalent rc file to enable sourced mode and virtual environment activation.

Verify before relying:

- Whether the package works reliably on non-Unix systems (classifiers list only Unix support).
- How well automatic sync handles version pinning, pre-release packages, or editable installs.
- Performance impact when managing large dependency trees.

## Package facts

- License: MIT (permissive)
- Python support: unspecified
- Install friction: low
- Maintenance: aging
- Downloads: 214.6K/month (top 15,000 on PyPI)
- Known vulnerabilities: none known

## Tags

auto-update requirements.txt, pip dependency sync, automatic requirements management, requirements.txt generator, pip wrapper for requirements, keep requirements.txt in sync, dependency tracking tool, dependency-management, pip-wrapper, requirements-sync

[View on SkillFed](https://skillfed.io/packages/to-requirements-txt) · [View on PyPI](https://pypi.org/project/to-requirements-txt/)