opentelemetry.exporter.jaegerNuGet · C# / .NET

Verdict

Looks abandoned

opentelemetry.exporter.jaeger appears abandoned — last commit this week. 12 of 121 open issues have had no reply. Plan a migration rather than waiting for a fix.

health 10/100

Why this verdict?

abandoned — No commits for over 365 days with unanswered issues piling up — or the registry marks it deprecated, or the repository is archived.

registry marks the package deprecated

Judged today from signal heuristics. How each verdict is decided

latest 1.5.1
licence Apache-2.0
stars 3,750
checked today
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

121

Unanswered

Contributors

What the project says about itself

Open milestones — Future 2/40 done; Exporter.Prometheus Stable Releases 33/40 done; v1.XY.0 (.NET 11 release tracking) (due 2026-11-15) 2/5 done. Source: the repository's milestones.
OpenSSF Scorecard — 8.5 / 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 yesterday; registry facts on every crawl.

State history 1

When	Change
2026-09-09	first verdict: abandoned

Badge

Drop this in your README. It re-renders itself as the verdict changes.

[![maintenance](https://isitdeadyet.dev/badge/nuget/opentelemetry.exporter.jaeger.svg)](https://isitdeadyet.dev/nuget/opentelemetry.exporter.jaeger)

Watch it

Get told when opentelemetry.exporter.jaeger 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.