Browser check · PyPI and npm

Why won’t this security alert close?

You upgraded and the alert is still open. Often every release that fixes it needs a newer Python or Node than you run, or a parent package asks for a range that leaves the fix out. Paste the package and its version, or your lock file, and say which Python or Node you run. For each open advisory the page shows the first release that fixes it, the runtime that release needs, whether yours can take it, and what you can do.

Check a package

Packages from

One per line: soupsieve==2.10, basic-ftp@5.3.1. Or paste requirements.txt with exact versions, pip freeze output, uv.lock, poetry.lock or package-lock.json (all of it, or the part your alert names). From a package-lock.json the page also finds the package that holds an old version in place.

Check sends each package name and version you paste to OSV.dev, private package names included. For each package with an advisory it asks PyPI or the npm registry for the public release list, and from an npm lock file also for the newest release of each package that holds an old version in place. Nothing else you paste leaves this page. What is sent where

Examples:

How the page decides

  • Advisories come from OSV.dev, which collects the GitHub Advisory Database and the Python Packaging Advisory Database. A record listed under two IDs (a GHSA and a PYSEC, say) counts once.
  • Fixed release means the first published release, newer than yours, that the advisory does not cover. Yanked releases and pre-releases don’t count. If a release fixes only some of the advisories, the page says which.
  • The runtime a release needs is what the package itself declares: Requires-Python on PyPI, engines.node on npm. pip and uv refuse a release whose Requires-Python leaves your Python out. npm only warns about engines unless engine-strict is set.
  • A version without its last part (3.11, or 22) is checked at both ends of that series. If the fix needs 3.11.5, the page says so instead of guessing your patch release.
  • Parent ranges (npm). From a package-lock.json, the page finds every package that depends on the vulnerable copy, checks whether its range admits a fixed release, and reads that parent’s newest release to see whether updating it would help.

What it doesn’t check

  • Whether your code reaches the vulnerable part. Each advisory says what it needs; read it before you decide to wait.
  • On Python, which package caps another (as some releases of gradio capped Pillow below 13). uv tree --invert --package NAME or pipdeptree -r -p NAME shows who asks for it.
  • Wheel availability for your platform, packages from your Linux distribution, Yarn and pnpm lock files, and private registries.

Doing it without this page

Your coding agent can do the same reads, or you can: run pip-audit or npm audit, open each advisory for the fixed version, then look up what that release needs with pip download PACKAGE==VERSION --no-deps on your Python, or npm view PACKAGE@VERSION engines, and npm explain PACKAGE for the parent. This page does those reads in one step and puts the answers side by side.

Walls we have tested

For these the page’s answer matches what we found by running the packages; the guides add which uses each advisory reaches, workarounds, and the exact resolver and scanner output.