@typespec/httpnpm
- latest 1.18.0
- last known licence MIT
- stars 5,948
- assessment attempted today
- GitHub evidence observed today
- registry checked 28 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 24 checks
Commits 90d
100
Open issues
991
Unanswered
407
Contributors
21
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 — 2. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — Backlog 428/1003 done; [2026] November (due 2026-11-06) 6/23 done; [2026] December (due 2026-12-04) 0/12 done; [2027] January (due 2027-01-08) 0/3 done; [2027] February (due 2027-02-05). Source: the repository's milestones.
Third-party facts checked 2 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-11-15 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@typespec/http)Watch it
Get told when @typespec/http 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.