Is mypy healthy, maintained, and safe?
Yes — mypy looks healthy, actively maintained, and free of known advisories today.
The verdict
On the OSPulse health scale, mypy lands at 100/100 — minimal risk, computed deterministically from live PyPI release history, and the OSV vulnerability database. Yes — mypy looks healthy, actively maintained, and free of known advisories today.
Its most recent release shipped on 13 July 2026 — 14 days ago — so development is clearly active. Across 139 releases the cadence has been steady, which is a good sign of an ongoing maintenance rhythm. PyPI doesn't expose a reliable maintainer count, so bus-factor isn't scored here — treat maintenance depth as unknown rather than assumed.
Security-wise, mypy currently has a clean OSV record — no published advisories. Keep in mind that reflects what's been disclosed, not a guarantee of safety.
The signals are green today, but a clean snapshot is not a standing guarantee — packages drift. This is a one-time snapshot of a single package — real projects depend on dozens or hundreds of packages, and any one of them can drift or be compromised between releases. Run your own requirements.txt through the free health check, or have OSPulse monitor your whole dependency tree continuously.
Evidence trail — deterministic, auditable
Key facts
- Latest version
- v2.3.0
- Last release
- 13 July 2026 (14 days ago)
- Total releases
- 139
- First release
- 9 September 2009
- Package age
- 16.9 years
- Maintainers
- not exposed by PyPI
- Known advisories
- 0
- Confidence
- High
Frequently asked
Is mypy still maintained?
Yes — mypy released as recently as 13 July 2026 (14 days ago), so it is actively maintained.
Does mypy have known security vulnerabilities?
No advisories are currently recorded for mypy in the OSV database. That means none have been publicly disclosed and indexed — it is not a guarantee of safety.
Is mypy safe to use?
Yes — mypy looks healthy, actively maintained, and free of known advisories today. OSPulse rates it 100/100 (minimal risk) based on release recency, cadence and known vulnerabilities.
Other PyPI packages we've checked
mypy is one package. What about the other hundreds in your tree?
Paste your own requirements.txt into the free health check for an instant snapshot — or let OSPulse monitor your whole dependency tree continuously, before your CVE scanner wakes up.
Data from the PyPI registry & OSV.dev · snapshot generated 2026-07-27 · scores are deterministic and recomputed on each refresh.