2ppyPyPI
- latest 1.7.1
- last known licence Apache-2.0
- stars 2
- assessment attempted 17 days ago
- GitHub evidence observed 17 days ago
- registry checked 20 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 23 months without a release, 2ppy published 1.7.1 on 2026-10-19.
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.10. Source: the registry.
- Open milestones — General usability 8/8 done; Make 2ppy a Pythonic library 7/7 done. Source: the repository's milestones.
- OpenSSF Scorecard — 2.5 / 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 17 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-20 | first verdict: finished |
Licence history 1
| When | Change | Severity |
|---|---|---|
| 2026-10-20 | Apache 2.0 License → Apache-2.0 (1.7.1) | info |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/pypi/2ppy)Watch it
Get told when 2ppy 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.