Opened 6 minutes ago
#37534 new Uncategorized
sqlparse is no longer maintained
| Reported by: | Colin Watson | Owned by: | |
|---|---|---|---|
| Component: | Uncategorized | Version: | 6.1 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
https://pypi.org/project/sqlparse/ now says:
"sqlparse is no longer actively maintained. Version 0.6.1 was its final release.
No further bug fixes, feature updates, or security fixes are planned. The repository and published packages will remain available, but users should not expect ongoing maintenance or security support.
Software Supply Chain Security: To minimize supply chain risks, I will retain control of the sqlparse project on PyPI and this GitHub repository. There are no plans to transfer ownership or grant publishing or commit access to third parties."
(See also https://www.openwall.com/lists/oss-security/2026/11/10/20, https://github.com/andialbrecht/sqlparse/discussions/945, and https://bugs.debian.org/1153985.)
I guess it isn't an ideal situation for Django to have a dependency that has no ongoing security support. I don't expect this to be trivial to address, since sqlparse is used by all Django's database backends. But: has anyone thought about what to do about this in the longer term?