@sentry/server-runtime-injectionnpm
- latest 11.6.0
- licence MIT
- stars 8,756
- assessment attempted 8 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 >=20.19.0 <22.0.0 || >=22.12.0 <23.0.0 || >=23.2.0. Source: the registry.
- Publishers on the registry — 1. Source: the registry.
- Open milestones — 11.0.0 55/55 done; OTEL 1/1 done; 12.0.0 0/6 done. Source: the repository's milestones.
- OpenSSF Scorecard — 5.8 / 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 8 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-10 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@sentry/server-runtime-injection)Watch it
Get told when @sentry/server-runtime-injection 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.