Is sqlalchemy healthy, maintained, and safe?
No — SQLAlchemy carries 3 unpatched critical advisories and should not be adopted without a remediation plan.
The verdict
On the OSPulse health scale, SQLAlchemy lands at 55/100 — medium risk, computed deterministically from live PyPI release history, and the OSV vulnerability database. No — SQLAlchemy carries 3 unpatched critical advisories and should not be adopted without a remediation plan.
Its most recent release shipped on 27 June 2026 — 29 days ago — so development is clearly active. Across 322 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.
OSV lists 6 known advisories for SQLAlchemy, including 3 critical. Open critical advisories are the strongest possible signal to pin to a patched version, replace, or fork before shipping. Each advisory is listed with its OSV/GHSA identifier below.
SQLAlchemy is usable but carries real signals — 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
Known vulnerabilities (6)
SQLAlchemy is vulnerable to SQL Injection via group_by parameter
SQLAlchemy vulnerable to SQL Injection via order_by parameter
SQLAlchemy vulnerable to SQL injection
Multiple SQL injection vulnerabilities in SQLAlchemy before 0.7.0b4, as used in Keystone, allow remote attackers to execute arbitrary SQL commands via the (1) limit or (2) offset keyword to the select
SQLAlchemy before 1.3.0b3 allows SQL Injection via the order_by parameter. The fix (commit 30307c4) was applied only to the main branch and was never backported to the 1.2.x release line; all 1.2.x ve
SQLAlchemy 1.2.17 has SQL Injection when the group_by parameter can be controlled.
Key facts
- Latest version
- v2.0.51
- Last release
- 27 June 2026 (29 days ago)
- Total releases
- 322
- First release
- 14 February 2006
- Package age
- 20.5 years
- Maintainers
- not exposed by PyPI
- Known advisories
- 6
- Confidence
- High
Frequently asked
Is SQLAlchemy still maintained?
Yes — SQLAlchemy released as recently as 27 June 2026 (29 days ago), so it is actively maintained.
Does SQLAlchemy have known security vulnerabilities?
Yes — OSV lists 6 advisories for SQLAlchemy, including 3 rated critical. See the advisory list on this page for the OSV/GHSA identifiers.
Is SQLAlchemy safe to use?
No — SQLAlchemy carries 3 unpatched critical advisories and should not be adopted without a remediation plan. OSPulse rates it 55/100 (medium risk) based on release recency, cadence and known vulnerabilities.
Other PyPI packages we've checked
sqlalchemy 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.