@useparagon/opentelemetry-instrumentation-httpnpm
- latest 0.0.8-canary.1
- last known licence Apache-2.0
- stars 3,490
- assessment attempted 23 days ago
- registry checked 6 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 1 check
The first observation is recorded. Trend lines appear once at least two checks have data for the same signal.
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — node >=14. Source: the registry.
- Publishers on the registry — 4. Source: the registry.
- Open milestones — Configs 16/16 done; Metrics After GA 5/11 done; OTLP Exporter GA 35/41 done; Logs API/SDK GA 58/58 done; SDK 3.0 (due 2026-10-15) 50/57 done. Source: the repository's milestones.
- OpenSSF Scorecard — 7.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 23 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-11 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@useparagon/opentelemetry-instrumentation-http)Watch it
Get told when @useparagon/opentelemetry-instrumentation-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.