@opentelemetry/exporter-jaeger 2.4.0

OpenTelemetry Exporter Jaeger allows user to send collected traces to Jaeger

@opentelemetry/exporter-jaeger@2.4.0 was published on 2026-01-14. Its manifest declares 4 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. The declared Node.js requirement is ^18.19.0 || >=20.6.0.

Deprecated: Package no longer supported. See https://github.com/open-telemetry/opentelemetry-js/pull/7098

All @opentelemetry/exporter-jaeger versions · Permanent reference to 2.4.0 · Latest release

Package specifications

Version2.4.0
License declarationApache-2.0
Published2026-01-14T17:05:35.833Z
Node.js requirement^18.19.0 || >=20.6.0
Type declarationsBundled declarations
Runtime dependency count4
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size62.85 KiB
Published file count18
Package typeNot declared
ES module entryNot declared
Default entrybuild/src/index.js
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies19
Repository stars3503
Repository forks1185

Install @opentelemetry/exporter-jaeger 2.4.0

npm install @opentelemetry/exporter-jaeger@2.4.0
pnpm add @opentelemetry/exporter-jaeger@2.4.0
yarn add @opentelemetry/exporter-jaeger@2.4.0

Runtime dependencies

Peer requirements

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review10/10 — all changesets reviewed
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Maintained10/10 — 30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions10/10 — GitHub workflow tokens follow principle of least privilege
Binary-Artifacts10/10 — no binaries found in the repo
License10/10 — license file detected
Signed-Releases0/10 — Project has not signed or included provenance with any releases.
Branch-Protection4/10 — branch protection is not maximal on development and all release branches
Security-Policy10/10 — security policy file detected
Pinned-Dependencies8/10 — dependency not pinned by hash detected -- score normalized to 8
Fuzzing0/10 — project is not fuzzed
SAST10/10 — SAST tool is run on all commits

Evidence and freshness