Know what a Python dependency update breaks before you merge it.
Python libraries rename and remove things from one release to the next, so a routine dependency update, from Dependabot, Renovate or you, can break code that used to work.
DepTime points to each line of your code an update breaks, says in which release it changed, and names what to use instead. No AI model in the loop: it runs on your machine, costs nothing, and gives the same answer every time. Your coding agent can use it too.
- Facts, not guesses. Answers come from comparing each library's own code release by release, and they show the evidence.
- Private and free. Open source (MIT) and runs on your machine. Your code and errors stay there.
- Honest about gaps. When it doesn't cover a package or can't tell, it says so instead of guessing.
Status: stable (1.0). The data updates itself twice a day. Spotted a wrong answer? Report it and it becomes a test case.
You need uv.
Check an update. After updating your lockfile or requirements, run this in your project:
uvx deptime check-upgradeIt compares your pinned versions with the last commit and exits with 1 when the update breaks something. To check every update pull request, add the GitHub Action.
Give your coding agent the same answers. Add DepTime to Claude Code:
claude mcp add deptime -- uvx deptime mcpOther AI coding tools (Cursor, Codex, VS Code, Claude Desktop and more) use the same command, uvx deptime mcp, in their MCP settings.
To make sure the agent uses it, paste this short block into your project's AGENTS.md (Codex and Cursor read it).
That's it. The first time it starts, DepTime downloads its data file (about 50 MB) and keeps it up to date on its own. To keep it fully offline, set DEPTIME_OFFLINE=1.
Using Claude Code? The plugin adds a /deptime:fix-upgrade command and suggests DepTime when a version error shows up:
/plugin marketplace add cschmertz/deptime
/plugin install deptime@deptime
First start timing out on a Mac?
If your uv is the Intel version (an Intel Mac, or Intel Homebrew on an Apple-silicon Mac), the first install has to compile one dependency, which can take a few minutes, longer than most apps wait. Run uvx deptime --help once in a terminal first; after that it starts in seconds.
On a pull request (from Dependabot, Renovate or a person), the GitHub Action marks each line the update breaks and fails the check only when something really breaks (setup guide):
# .github/workflows/upgrade-check.yml
on:
pull_request:
paths: ["**/uv.lock", "**/poetry.lock", "pyproject.toml", "**/requirements*.txt", "**/requirements/**"]
permissions:
contents: read
jobs:
check:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v7 # pin to a commit in your own workflows
- uses: cschmertz/deptime@v1.0.3You can run the same check from a terminal with uvx deptime check-upgrade, or in Claude Code with /deptime:fix-upgrade, which also has Claude fix what broke.
Tried on 264 real update pull requests, it caught all 13 that broke their project and raised a false alarm on 2 (results). With /deptime:fix-upgrade, Claude fixed 86.7% of 60 broken updates it hadn't seen before, against 76.7% on its own, in about half the steps (results).
When an import or call into a library fails, your agent (or you, from a terminal) passes the error to DepTime and gets back what changed, in which release, and what to use instead:
In plain words:
httpx.Client.init accepted
proxiesup to httpx 0.27.2; it is gone from 0.28.0 onward. Deprecated in 0.26.0 ("The 'proxies' argument is now deprecated. Use 'proxy' or 'mounts' instead."). Useproxyormountsinstead, or pin httpx<=0.27.2.
The full answer your agent receives
{
"symbol": "httpx.Client.__init__(proxies)",
"issue": "param_removed",
"installed_version": "0.28.1",
"last_version_with": "0.27.2",
"first_version_without": "0.28.0",
"deprecated_in": "0.26.0",
"replacements": [
{"target": "proxy", "confidence": 0.8, "source": "deprecation_message"},
{"target": "mounts", "confidence": 0.79, "source": "deprecation_message"}
],
"pin_to_restore": "httpx<=0.27.2",
"confidence": "high"
}That's the real answer from the published data, trimmed. The full answer also quotes the warning DepTime found in httpx's own code.
Your agent can ask whether a function or argument it remembers still exists in the version you have installed, or what changed between two versions (or since a date, such as its training cutoff).
Migrating by hand? The rename maps show what the MCP SDK 2, LangChain 1, pydantic 2, openai 1 and httpx 0.28 migrations renamed or removed, and what replaces each name, from the same data.
| Tool | What it's for |
|---|---|
explain_error |
An import or call into a library just failed |
check_upgrade |
You're updating a dependency: which lines of your code break? |
check_symbols |
Check names and arguments against the version you have installed |
diff_versions |
Everything that changed between two versions, or since a date |
symbol_history |
The full history of one function or class |
coverage |
Which libraries DepTime knows (53 fast-moving packages, mostly the AI and agent stack: list) |
Every answer says how sure it is and why. The exact inputs and outputs are in the product spec.
Every number below is a first try: the test cases and their right answers were collected before DepTime ever saw them.
| How often does it… | First try | Tested on |
|---|---|---|
| name the right library, function and release from a real error? | 87% (166 of 191) | Errors from GitHub issues and Stack Overflow |
| …and an AI model alone, from memory? | 82% to 84% (Claude Sonnet 5.5 and Opus 5.5), 66% to 69% (Claude Haiku 5.5), 59% (DeepSeek V4.1 Flash), 19% (Qwen3.5 9B) | The same 191 errors |
| suggest the right replacement in its top three? | 48% (41 of 85) | The same errors, where a replacement exists |
| wrongly flag code that still works after an update? (lower is better) | 0.1% (2 of 2,047) | Real projects, checked by actually running them |
| find the code an update breaks? | 100% (147 of 147) | The same projects |
| …and an AI model alone, from memory? | Breaks found / working code flagged: 91% / 0.2% (Claude Sonnet 5.5), 74% / 0.3% (Claude Haiku 5.5), 81% / 2.7% (DeepSeek V4.1 Flash), 31% / 15% (Qwen3.5 9B) | The same projects, scored so that "can't tell" counts as not flagged: DepTime then finds 96.7% |
- Checking updates is its strongest skill. It finds nearly every break and almost never cries wolf. The rows on projects are from the newest of six test sets; across all six, it found 95.9% to 100% of breaks and wrongly flagged 0.05% to 3.8% of working code.
- It helps smaller models most. The best Claude models come close on their own; smaller and cheaper ones fall well behind.
- Suggesting replacements is its weakest skill. It gets the right one about half the time, so it tells your agent how confident it is.
Every test set and result is in the benchmark, re-checked automatically on every change. The test sets are also published on their own, with a scorer, so any other tool or model can be measured the same way: the API-change benchmark.
- It covers the libraries on its list, not all of PyPI. For anything else it says "not covered".
- It reads code without running it. A few names that only appear while a library runs can come back as
unknown. - It sees names and arguments, not behaviour. If a function keeps its name but does something different, DepTime can't tell, so keep running your tests.
- Python only.
Twice a day, GitHub reads each new release of every covered library (without running it), compares it with the release before, and publishes the result as one signed file. DepTime downloads that file and answers every question on your machine, in milliseconds. More in the architecture doc.
Claude Code, Claude Desktop, Cursor, VS Code, Codex and any app that speaks MCP, on Linux, macOS and Windows, with Python 3.12 to 3.15. From a fresh install to the first answer takes about 10 seconds on Linux and Mac and 20 on Windows (client tests, first-start tests).
Command line
uvx deptime explain --installed httpx==0.28.1 < traceback.txt
uvx deptime history httpx Client.__init__
uvx deptime check httpx 0.28.1 'httpx.Client:proxies,proxy'
uvx deptime diff httpx 0.27.2 0.28.1
uvx deptime diff pydantic 2024-06-01 # everything since a date
uvx deptime check-upgrade # what the lockfile change breaks; exit 1 on a break
uvx deptime index status | pullHosting it yourself
For web apps that only accept a URL, run deptime serve on any container host (a Dockerfile and fly.toml are included). See self-hosting.
Built on griffe, which reads the libraries' code.
How it differs from docs tools like Context7 and Ref: they show the docs for a version; DepTime tells you when something changed and what replaced it.
The most helpful thing you can send is a wrong answer: each one becomes a test case. See CONTRIBUTING.md. To work on the code:
uv sync && uv run pytestMore: Product spec · Architecture · Privacy & security · Benchmark · Changelog · License (MIT)