NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →

PackageTrack

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 account

One package, as the archive shows it

2.29.02.32.226 Apr 202321 May 2024
1 of 6
From
To

requests 2.29.0 to 2.32.2: 2 withdrawn versions, 2 security fixes, 1 breaking change

  1. Withdrawn2.32.020 May 2024

    “Yanked due to conflicts with CVE-2024-35195 mitigation”

  2. Withdrawn2.32.120 May 2024

    “Yanked due to conflicts with CVE-2024-35195 mitigation”

  3. Security2.31.022 May 2023

    “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…”

  4. Security2.32.221 May 2024

    “…is subject to the same issue described in CVE-2024-35195 .”

1 more release in this range
  1. 2.30.0BreakingThis may contain minor breaking changes so we advise careful testing and reviewing https://urllib3.readthedocs.io/en/latest/v2-migration-guide.html pr…

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. 1

    Send your lock file or manifest.

    Run packagetrackdev push in the project, or add the GitHub Action to CI. Both send package names and versions, nothing else.

  2. 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. 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.

Subject: PackageTrack: 1 withdrawn version, CVE-2026-116689, 5 packages behind

1 withdrawn version, CVE-2026-116689, 5 packages behind

Your daily digest for 2 projects: api, web.

Withdrawn versions in your builds1

WITHDRAWNapi: starlette 0.41.1 (pulled in by fastapi)

“python-multipart release was broken”

Behind today5

api

fastapi0.115.4 → 0.162.5151 behind
starlette0.41.1 → 1.10.041 behind
cryptography48.0.0 → 50.0.25 behind

web

axios1.21.0 → 1.21.11 behind
next16.4.5 → 16.4.61 behind
Open your dashboard
What changed

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.”

Excerpt of the daily mail

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 | sh

Windows (PowerShell)

irm https://packagetrack.dev/install.ps1 | iex

Scripts blocked on this machine? Install by hand, checking each file yourself.

Then, for Claude Code

claude mcp add -s user packagetrackdev -- packagetrackdev-mcp

Cursor 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.

Know what changed in yours.

Create an account