aiohttp-ssePyPI
- latest 3.0
- last known licence Apache 2
- stars 237
- assessment attempted 27 days ago
- GitHub evidence observed 27 days ago
- registry checked 27 days ago
- registry ↗
- repository ↗
Vulnerabilities, end of life and next steps
Check a specific version for known advisories, documented mitigations and evidence-backed earlier-version options. Maintenance health is separate from vulnerability status.
Review remediation options →Came back
After 2 years without a release, aiohttp-sse published 3.0 on 2026-10-11.
Usually this is a maintainer returning. It is also what a hijacked package looks like, so it is worth a glance at what changed before you upgrade.
Maintenance trends
Loading historical repository activity…
Signals · last 2 checks
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — python >=3.11. Source: the registry.
- OpenSSF Scorecard — 5.1 / 10 on 2026-08-24. Source: OpenSSF, via deps.dev. A third party's view of security practice, not part of the health score.
Third-party facts checked on 2026-09-25; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-20 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/pypi/aiohttp-sse)
Watch it
Get told when aiohttp-sse changes state, changes licence, or is deprecated — instead of finding out during an incident.
Free for up to 25 packages. Signing in is a link sent to your email — there is no password to choose.