Dependency health Workspace Pro coming soon

a3mPyPI

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 2 years without a release, a3m published 0.8.3 on 2026-10-29.

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.

What the project says about itself
  • Build provenance — the latest release, 0.8.3, carries a signed provenance attestation. Source: the registry.
  • Supported runtime — python >=3.12. Source: the registry.
  • OpenSSF Scorecard — 3.6 / 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 7 days ago; registry facts on every crawl.

State history 1
WhenChange
2026-10-30 first verdict: finished

Badge

maintenance: finished

Drop this in your README. It re-renders itself as the verdict changes.

[![maintenance](https://isitdeadyet.dev/badge/pypi/a3m.svg)](https://isitdeadyet.dev/pypi/a3m)

Watch it

Get told when a3m 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.