@bbc/http-transportnpm
- latest 5.0.1
- last known licence Apache-2.0
- stars 14
- assessment attempted 11 days ago
- GitHub evidence observed 11 days ago
- registry checked 11 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 →Came back
After 22 months without a release, @bbc/http-transport published 5.0.1 on 2026-10-14.
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.
Maintenance trends
Loading historical repository activity…
Signals · last 2 checks
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — node >=24.0.0. Source: the registry.
- Publishers on the registry — 36. Source: the registry.
- Open milestones — v3.5.0 2/2 done; v3.5.2 1/1 done. Source: the repository's milestones.
- OpenSSF Scorecard — 4 / 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 on 2026-09-29; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-27 | first verdict: coasting |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@bbc/http-transport)Watch it
Get told when @bbc/http-transport 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.