@azure-tools/azure-http-specsnpm
- latest 0.1.0-alpha.46
- last known licence MIT
- stars 27
- assessment attempted 18 days ago
- GitHub evidence observed 18 days ago
- registry checked 18 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
100
Open issues
407
Unanswered
186
Contributors
17
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — node >=22.0.0. Source: the registry.
- Publishers on the registry — 3. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — Backlog 77/248 done; [2026] October (due 2026-10-02) 2/26 done; [2026] November (due 2026-11-06) 0/11 done; [2026] December (due 2026-12-04); [2027] January (due 2027-01-08). Source: the repository's milestones.
Third-party facts checked on 2026-09-22; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-19 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@azure-tools/azure-http-specs)Watch it
Get told when @azure-tools/azure-http-specs 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.