Dependency health Workspace

pyprojPyPI

Vulnerabilities, end of life and next steps

Check a specific version for known advisories, documented mitigations and evidence-backed earlier-version options. Maintenance health is separate from vulnerability status.

Review remediation options →

Came back

After 13 months without a release, pyproj published 3.8.0 on 2026-09-05.

Usually this is a maintainer returning. It is also what a hijacked package looks like, so it is worth a glance at what changed before you upgrade.

What the project says about itself
  • Build provenance — the latest release carries no provenance attestation. Source: the registry.
  • Supported runtimepython >=3.12. Source: the registry.
  • Open milestones4.0.0 0/1 done; 3.8.1 0/1 done. Source: the repository's milestones.
  • OpenSSF Scorecard5.5 / 10 on 2026-08-17. Source: OpenSSF, via deps.dev. A third party's view of security practice, not part of the health score.

Third-party facts checked today; registry facts on every crawl.

State history 1
WhenChange
2026-09-06 first verdict: active

Badge

maintenance: active

Drop this in your README. It re-renders itself as the verdict changes.

[![maintenance](https://isitdeadyet.dev/badge/pypi/pyproj.svg)](https://isitdeadyet.dev/pypi/pyproj)

Watch it

Get told when pyproj changes state, changes licence, or is deprecated — instead of finding out during an incident.

Free for up to 25 packages. Signing in is a link sent to your email — there is no password to choose.