Know what changed,
before it breaks something.
PackageTrack follows every dependency in your project and tells you once a day what changed in them, withdrawn versions and security changes first, in the maintainers' own words.
Create an accountOne package, as the archive shows it
requests 2.29.0 to 2.32.2: 2 withdrawn versions, 2 security fixes, 1 breaking change
“Yanked due to conflicts with CVE-2024-35195 mitigation”
“Yanked due to conflicts with CVE-2024-35195 mitigation”
“Versions of Requests between v2.3.0 and v2.30.0 are vulnerable to potential forwarding of Proxy-Authorization headers to destination servers when foll…”
“…is subject to the same issue described in CVE-2024-35195 .”
With an account, you get this for every dependency in your project.
The release that matters is the one nobody read.
Release notes sit in changelogs, GitHub releases and registry pages, somewhere different for every package. A lock file can hold hundreds of packages, most of them pulled in by something else. So the version that was withdrawn, or the one that fixes a CVE, looks like every other bump in the diff.
Set up once.
- 1
Send your lock file or manifest.
Run
packagetrackdev pushin the project, or add the GitHub Action to CI. Both send package names and versions, nothing else. - 2
Read one mail a day.
Withdrawn versions in your builds come first, then how far behind each dependency is, then what changed in the versions in between. Daily, weekly or monthly, your choice. When everything is current, no mail.
- 3
Send alerts where your team works.
When a version you run is withdrawn, or a new release's notes name a CVE, you hear about it the same day in Slack, Discord or your own endpoint.
What arrives.
1 withdrawn version, CVE-2026-116689, 5 packages behind
Your daily digest for 2 projects: api, web.
WITHDRAWNapi: starlette 0.41.1 (pulled in by fastapi)
“python-multipart release was broken”
api
| fastapi | 0.115.4 → 0.162.5 | 151 behind |
| starlette | 0.41.1 → 1.10.0 | 41 behind |
| cryptography | 48.0.0 → 50.0.2 | 5 behind |
web
| axios | 1.21.0 → 1.21.1 | 1 behind |
| next | 16.4.5 → 16.4.6 | 1 behind |
axios 1.21.1
SECURITY“follow-redirects: Raised the follow-redirects range from ^1.16.0 to ^1.16.2 to fix CVE-2026-116689 (GHSA-mrwp-f3q8-3g9p).”
cryptography 49.0.0
BREAKING“BACKWARDS INCOMPATIBLE: Support for x86_64 macOS has been removed.”
A report for every project.
Withdrawn and deprecated versions in this build, packages behind, and what changed. Breaking and Security labels sit next to the sentence that earns them.
Your coding agent reads it too.
With the MCP server, Claude Code, Cursor and other agents read the release notes between your version and the target before they upgrade. Looking up a package needs no account.
macOS, Linux
curl -fsSL https://packagetrack.dev/install.sh | shWindows (PowerShell)
irm https://packagetrack.dev/install.ps1 | iexScripts blocked on this machine? Install by hand, checking each file yourself.
Then, for Claude Code
claude mcp add -s user packagetrackdev -- packagetrackdev-mcpCursor and Windsurf: add packagetrackdev-mcp under mcpServers. VS Code: under servers.
Eight registries.
- PyPI
- uv.lock, poetry.lock, Pipfile.lock
- npm
- package-lock.json, pnpm-lock.yaml, yarn.lock, bun.lock
- crates.io
- Cargo.lock
- Packagist
- composer.lock
- NuGet
- packages.lock.json
- pub.dev
- pubspec.lock
- Go
- go.mod
- Maven Central
- gradle.lockfile
No lock file? package.json, requirements.txt and pom.xml work too, for direct dependencies.
Every package page is public. Browse the archive.
Free.
One account type, no card. Up to 20 projects, 5 members and 3 webhook endpoints per organization.