
Python Package Documentation
The Python Package Index, reimagined.
PyPI tells you a package exists. Not whether to trust it, or what an upgrade will break. pypx puts the full context on one page: • Changelogs from GitHub and GitLab • Known CVEs from OSV • Downloads, install size, platforms • Release cadence — is this still alive? • The dependency tree • Real API docs, in the browser • A diff of the public API between any two versions That last one is your upgrade check: see which signatures changed before you bump. Every page has a plain-text twin, so your agents get the same context you do. Free, no account, no tracking. Open source.

PyPI tells you a package exists. Not whether to trust it, or what an upgrade will break. pypx puts the full context on one page: • Changelogs from GitHub and GitLab • Known CVEs from OSV • Downloads, install size, platforms • Release cadence — is this still alive? • The dependency tree • Real API docs, in the browser • A diff of the public API between any two versions That last one is your upgrade check: see which signatures changed before you bump. Every page has a plain-text twin, so your agents get the same context you do. Free, no account, no tracking. Open source.
1 comment
Bumping a version and hoping was basically my whole process. pypx gives you the full context first: changelog, CVEs, a diff of the API. Your agents read the same page. How do you vet an upgrade?