apify-sharedPyPI
- latest 2.3.0
- last known licence Apache-2.0
- stars 2
- assessment attempted 16 days ago
- GitHub evidence observed 16 days ago
- registry checked 16 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 →Maintenance trends
Loading historical repository activity…
Signals · last 2 checks
Commits 90d
6
Open issues
0
Unanswered
0
Contributors
7
What the project says about itself
- Build provenance — the latest release, 2.3.0, carries a signed provenance attestation. Source: the registry.
- Supported runtime — python >=3.10. Source: the registry.
- Open milestones — 127th sprint - Tooling team (due 2025-11-17); 128th sprint - Infrastructure team (due 2025-12-01); 128th sprint - Tooling team (due 2025-12-01); 128th sprint - Web team (due 2025-12-02); 129th sprint - Tooling team (due 2025-12-15) 2/2 done. Source: the repository's milestones.
Third-party facts checked on 2026-10-08; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-23 | first verdict: dead |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/pypi/apify-shared)Watch it
Get told when apify-shared 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.