azure-cli-batchPyPI
- latest 4.0.3
- licence MIT
- stars 4,650
- assessment attempted yesterday
- GitHub evidence observed yesterday
- 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
100
Open issues
3508
Unanswered
4
Contributors
58
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — Backlog 3703/6015 done; April 2026 (2026-04-07) (due 2026-03-31) 132/140 done; May 2026 (2026-05-05) (due 2026-04-28) 140/142 done; June 2026 (2026-06-02) (due 2026-05-26) 124/138 done; July 2026 (2026-07-07) (due 2026-06-30) 149/171 done. Source: the repository's milestones.
- OpenSSF Scorecard — 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 yesterday; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-17 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/pypi/azure-cli-batch)Watch it
Get told when azure-cli-batch 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.