autopwn-suitePyPI
- latest 2.8.1
- last known licence Apache-2.0
- stars 1,146
- assessment attempted today
- GitHub evidence observed today
- registry checked today
- 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 4 years without a release, autopwn-suite published 2.8.1 on 2026-10-23.
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, 2.8.1, carries a signed provenance attestation. Source: the registry.
- Supported runtime — python <4.0,>=3.10. Source: the registry.
- Security policy — published. Source: the repository.
Third-party facts checked 14 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-26 | first verdict: active |
Licence history 1
| When | Change | Severity |
|---|---|---|
| 2026-10-26 | EULA → Apache-2.0 (2.8.1) | warning |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/pypi/autopwn-suite)Watch it
Get told when autopwn-suite 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.