All projects matching “package upgrade”

PyPI breaking changes between two versions of a Python package, before a pip package upgrade: the documented breaking changes per version from the project's CHANGELOG, HISTORY or CHANGES file and GitHub release notes (alpha/beta/rc folded into the major), plus Requires-Python and required dependency changes, yanked versions, migration guide links and a verdict. PEP 440 versions ('1.10.13', '2.0')

Vulnerability scan for a list of packages in one call via OSV.dev: GET ?packages=lodash@4.17.15,pypi:requests==2.19.0,go:github.com/gin-gonic/gin@v1.9.0 (or POST a lockfile). Up to 200 across npm, PyPI, Go, crates.io, Maven and more: per-package advisories, severity, fix versions and upgrade targets; hallucinated and malicious packages flagged. JSON.

Audit a whole dependency manifest in one call before installing or upgrading. Send a package.json, a requirements.txt, or npm and PyPI package lists (up to 50 packages). Per dependency: latest version and publish date, whether your pin is behind, license, deprecation or yanked status, weekly npm downloads, and known vulnerabilities from OSV with severity and first fixed version. Deterministic, no

Use this before adding or upgrading an npm dependency (OpenZeppelin, solmate, hardhat…), or to triage a lockfile: GitHub/OSV advisories affecting a whole package-lock.json or yarn.lock (or up to 100 listed packages) at their exact pinned versions. Instant, per request.