ambi-alertPyPI
- latest 0.0.2
- stars 4
- assessment attempted 20 days ago
- GitHub evidence observed 20 days ago
- registry checked 26 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
20
Open issues
17
Unanswered
13
Contributors
2
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — python <4.0,>=3.10. Source: the registry.
- Open milestones — Custom Connectors (Composio) 8/10 done; SEO 10/10 done; Rebrand: webwhen.ai 31/31 done; UX Polish & Bug Fixes (due 2025-11-16) 4/5 done; API-First Platform (due 2025-11-19) 5/7 done. Source: the repository's milestones.
Third-party facts checked 20 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-28 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/pypi/ambi-alert)
Watch it
Get told when ambi-alert 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.