@opentelemetry/exporter-jaeger 0.3.0
OpenTelemetry Exporter Jaeger allows user to send collected traces to Jaeger
@opentelemetry/exporter-jaeger@0.3.0 was published on 2019-12-13. Its manifest declares 5 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=8.0.0.
Deprecated: Package no longer supported. See https://github.com/open-telemetry/opentelemetry-js/pull/7098
All @opentelemetry/exporter-jaeger versions · Permanent reference to 0.3.0 · Latest release
Package specifications
| Version | 0.3.0 |
|---|---|
| License declaration | Apache-2.0 |
| Published | 2019-12-13T19:37:02.969Z |
| Node.js requirement | >=8.0.0 |
| Type declarations | Bundled declarations |
| Runtime dependency count | 5 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 32.40 KiB |
| Published file count | 11 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | build/src/index.js |
| Side effects declaration | Not declared |
| Direct advisories | Unknown |
| Resolved graph dependencies | Unknown |
| Repository stars | 3503 |
| Repository forks | 1185 |
Install @opentelemetry/exporter-jaeger 0.3.0
npm install @opentelemetry/exporter-jaeger@0.3.0 pnpm add @opentelemetry/exporter-jaeger@0.3.0 yarn add @opentelemetry/exporter-jaeger@0.3.0
Runtime dependencies
- jaeger-client ^3.15.0
- @opentelemetry/base ^0.3.0
- @opentelemetry/core ^0.3.0
- @opentelemetry/types ^0.3.0
- @opentelemetry/tracing ^0.3.0
Peer requirements
- None declared
Optional dependencies
- None declared
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-Review | 10/10 — all changesets reviewed |
|---|---|
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Maintained | 10/10 — 30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Token-Permissions | 10/10 — GitHub workflow tokens follow principle of least privilege |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| License | 10/10 — license file detected |
| Signed-Releases | 0/10 — Project has not signed or included provenance with any releases. |
| Branch-Protection | 4/10 — branch protection is not maximal on development and all release branches |
| Security-Policy | 10/10 — security policy file detected |
| Pinned-Dependencies | 8/10 — dependency not pinned by hash detected -- score normalized to 8 |
| Fuzzing | 0/10 — project is not fuzzed |
| SAST | 10/10 — SAST tool is run on all commits |
Evidence and freshness
- https://registry.npmjs.org/%40opentelemetry%2Fexporter-jaeger/0.3.0 — retrieved 2026-11-01T06:26:47.994Z
- https://api.deps.dev/v3/projects/github.com%2Fopen-telemetry%2Fopentelemetry-js — retrieved 2026-11-01T03:08:27.797Z