autonormalizePyPI
- latest 2.0.1
- licence BSD 3-clause
- stars 118
- assessment attempted 6 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 1 check
The first observation is recorded. Trend lines appear once at least two checks have data for the same signal.
Commits 90d
0
Open issues
15
Unanswered
10
Contributors
0
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — python >=3.7, <4. Source: the registry.
- Open milestones — 2020 Phase 2 (due 2020-04-20); 2020 Phase 3 (due 2020-05-25); August Milestone (due 2020-08-31). 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 6 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-13 | first verdict: finished |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/pypi/autonormalize)Watch it
Get told when autonormalize 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.