depcheckr 0.1.2

Effortlessly inspect and upgrade dependencies in your pyproject.toml

📦 depcheckr

The smart, modern way to manage your Python dependencies.

Inspect, compare, and upgrade dependencies in your pyproject.toml — with style and safety.

---

🚀 Features

• 📖 Inspect your dependencies and check if they’re up to date
• 📈 Get clear update types: major, minor, patch, or up-to-date
• 🔁 Upgrade individual packages or all at once
• 🧪 Dry-run support so nothing breaks accidentally
• 💄 Beautiful CLI powered by Typer and Rich
• 🦄 Python 3.11+ native — built with modern tooling and async speed

---

📥 Installation

pip install depcheckr

💡 Make sure your project is initialized as a Git repository:

git init

---

🛠 Usage

🔍 Inspect dependencies

depcheckr inspect show

Or inspect dev dependencies:

depcheckr inspect show --group dev

♻️ Upgrade dependencies

Upgrade one or more specific packages:

depcheckr upgrade apply --upgrade django httpx

Upgrade all outdated packages:

depcheckr upgrade apply --upgrade-all

Preview changes without writing to file:

depcheckr upgrade apply --upgrade-all --dry-run

---

✅ Git Commit Conventions

depcheckr follows the Conventional Commits standard. This is required for changelog automation and GitHub release notes.

Examples

• feat: add support for --upgrade-all
• fix: correct version parsing issue
• chore: bump version to 0.2.0

Hooks and Automation

This repo uses pre-commit and commitlint to enforce commit standards.

Install pre-commit hooks:

pre-commit install

Your commits will now be linted automatically.

Optional: Use Commitizen (interactive prompt)

You can install Commitizen:

npm install -g commitizen cz-conventional-changelog

Then run:

cz

Or, if you're using Bun and already initialized the repo with Git:

bun x cz

If using Lazygit, add this to ~/.config/lazygit/config.yml:

customCommands:
  - key: "C"
    context: "files"
    command: "cz commit"
    description: "Commit using Commitizen"
    subprocess: true

---

🧪 Requirements

• Python 3.11 or newer
• Git (ensure repo is initialized with git init)

---

📦 Packaging and Development

To build locally with uv:

uv venv
uv pip install -e .
depcheckr inspect show

To publish:

uv build
uv pip install twine
python -m twine upload dist/*

---

🤝 Contributing

Contributions are welcome! To get started:

1. Fork the repo and clone it locally
2. Install dependencies with uv pip install -e .
3. Set up the pre-commit hooks: pre-commit install
4. Use conventional commits via cz or cz commit
5. Run tests and lint before opening a PR

Please follow the Conventional Commits format and ensure all checks pass before submitting pull requests.

---

🪪 License

MIT License © 2025 Patrick Mazulo