Is MySQL-python healthy, maintained, and safe?
Probably not. MySQL-python has gone quiet for over two years and shows the hallmarks of an abandoned package.
The verdict
MySQL-python earns a health score of 40/100, a medium risk rating, computed deterministically from live PyPI release history, and the OSV vulnerability database. Probably not. MySQL-python has gone quiet for over two years and shows the hallmarks of an abandoned package.
The last sign of life was 2 January 2014, more than 12 years ago (4638 days). By any practical measure the package looks abandoned. Historically it released far more frequently, so the current silence reads as a genuine collapse in velocity rather than a natural gap. 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, MySQL-python currently has a clean OSV record, with no published advisories. Keep in mind that reflects what's been disclosed, not a guarantee of safety.
MySQL-python is usable but carries real signals, so pin versions, watch for new advisories, and keep a fallback in mind. 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
- v1.2.5
- Last release
- 2 January 2014 (4638 days ago)
- Total releases
- 13
- First release
- 6 March 2007
- Package age
- 19.5 years
- Maintainers
- not exposed by PyPI
- Known advisories
- 0
- Confidence
- High
Frequently asked
Is MySQL-python still maintained?
It doesn't appear to be. The last release was 2 January 2014, over two years ago, which usually indicates an abandoned package.
Does MySQL-python have known security vulnerabilities?
No advisories are currently recorded for MySQL-python in the OSV database. That means none have been publicly disclosed and indexed, so it is not a guarantee of safety.
Is MySQL-python safe to use?
Probably not. MySQL-python has gone quiet for over two years and shows the hallmarks of an abandoned package. OSPulse rates it 40/100 (medium risk) based on release recency, cadence and known vulnerabilities.
Other PyPI packages we've checked
MySQL-python 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-09-14 · scores are deterministic and recomputed on each refresh.