SQLModel looks unmaintained. The PRs are languishing in purgatory waiting for the submitters to croak from old age. I died a little inside (see imdb all reviews must start with a drama queen comment like this) noticing the PR count has just achieved 70 PRs as of today. Which must be an achievement in project mismanagement.
According only from the release notes, the last real release was sqlmodel-0.0.23 on Feb 28th 2025. For those keeping score today is Aug 8th 2025
Most activity is bots upgrading gh actions and precommit autoupdate. aka commit spam.
The last human commit was Jun 19th fixing some tests for the docs.
This is a sell point for litestar. Bypassing pydantic also bypasses the horror show of SQLModel.
Yeah, it’s unmaintained because one guy, tiangolo, is the only maintainer for both of those projects, and he doesn’t let anyone else approve PRs and so on. I think Litestar has a much better organisation structure.
Probably most projects are as guilty as tiangolo. Myself included. How to scale to multiple maintainers? Tell me about your experience. Would like to know how to avoid this trap.
This seems to be a github weakness. Each of us individually contributes by making a great package. Folks start using it and situation does not scale.
Dear OP
SQLModel looks unmaintained. The PRs are languishing in purgatory waiting for the submitters to croak from old age. I died a little inside (see imdb all reviews must start with a drama queen comment like this) noticing the PR count has just achieved 70 PRs as of today. Which must be an achievement in project mismanagement.
According only from the release notes, the last real release was sqlmodel-0.0.23 on Feb 28th 2025. For those keeping score today is Aug 8th 2025
Most activity is bots upgrading gh actions and precommit autoupdate. aka commit spam.
The last human commit was Jun 19th fixing some tests for the docs.
This is a sell point for litestar. Bypassing pydantic also bypasses the horror show of SQLModel.
Will look into msgspec+litestar
Yeah, it’s unmaintained because one guy, tiangolo, is the only maintainer for both of those projects, and he doesn’t let anyone else approve PRs and so on. I think Litestar has a much better organisation structure.
Probably most projects are as guilty as tiangolo. Myself included. How to scale to multiple maintainers? Tell me about your experience. Would like to know how to avoid this trap.
This seems to be a github weakness. Each of us individually contributes by making a great package. Folks start using it and situation does not scale.
Rinse wash repeat
I have next to no experience with managing open source projects :P