acroPyPI
- latest 1.0.2
- last known licence MIT
- stars 27
- assessment attempted 26 days ago
- GitHub evidence observed 26 days ago
- registry checked 28 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
21
Open issues
17
Unanswered
7
Contributors
11
What the project says about itself
- Build provenance — the latest release, 1.0.2, carries a signed provenance attestation. Source: the registry.
- Supported runtime — python >=3.10. Source: the registry.
- Open milestones — SACRO_Adding more functionality to python 4/5 done; D2.5 Front Door Risk Aggregator (due 2026-03-01); D3.2 Productionised SACRO (due 2026-03-31) 24/24 done; D2.6 Meta-data drive disclosure control for federated analytics (due 2026-10-01) 15/25 done; Re-aggregating tables as a mitigation strategy (due 2027-02-26) 0/1 done. Source: the repository's milestones.
Third-party facts checked 26 days ago; 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/acro)
Watch it
Get told when acro 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.