Is trio-websocket still maintained?
🟡 Slowing
trio-websocket has had no release in over a year. The latest release, 0.12.2, came out on 2025-02-25 (632 days ago), with 0 release(s) in the past 12 months. The source repository was last pushed on 2025-10-21.
- Is trio-websocket deprecated? No deprecation signal found: the repository isn't archived, and the latest release doesn't declare itself inactive. (A deprecation notice in the README or docs is not checked.)
- Is trio-websocket dead or abandoned? Possibly: no release for 632 days and no push since 2025-10-21.
Checked 2026-11-19 03:52 UTC. Status is a mechanical reading of public signals (method), not a quality judgement: a finished library can release rarely and still be safe to use.
| Signal | Value | Source |
|---|---|---|
| Latest stable version | 0.12.2 (2025-02-25) | PyPI |
| Newer pre-release | - | deps.dev |
| Last release of any kind | 2025-02-25 (632 days ago) | deps.dev |
| Releases in the past 12 months | 0 | deps.dev |
| Declared inactive (PyPI classifier) | no | PyPI |
| Source repository | github.com/python-trio/trio-websocket | deps.dev |
| Repository archived | no | GitHub API |
| Last push to the repository | 2025-10-21 | GitHub API |
| OpenSSF Scorecard "Maintained" (0–10) | - | deps.dev |
| Stars / open issues | 81 / 22 | deps.dev |
| Downloads, last 30 days | 28,815,739 (rank 676) | top-pypi-packages |
Data: trio-websocket.json · all packages: all.json, CSV · source: JasonTKG/pypi-maintenance-status (refreshed weekly). Not affiliated with PyPI or the PSF.