@opentelemetry/propagation-utils 0.31.18

Propagation utilities for opentelemetry instrumentations

@opentelemetry/propagation-utils@0.31.18 was published on 2026-04-17. Its manifest declares 0 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: The use of process spans has been removed from Messaging Semantic Conventions. It is now recommended to connect pub/sub spans via Span Links. See https://opentelemetry.io/docs/specs/semconv/messaging/messaging-spans/ for details.

All @opentelemetry/propagation-utils versions · Permanent reference to 0.31.18 · Latest release

Package specifications

Version0.31.18
License declarationApache-2.0
Published2026-04-17T14:41:58.963Z
Node.js requirement^18.19.0 || >=20.6.0
Type declarationsBundled declarations
Runtime dependency count0
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size59.29 KiB
Published file count18
Package typeNot declared
ES module entryNot declared
Default entrybuild/src/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars938
Repository forks728

Install @opentelemetry/propagation-utils 0.31.18

npm install @opentelemetry/propagation-utils@0.31.18
pnpm add @opentelemetry/propagation-utils@0.31.18
yarn add @opentelemetry/propagation-utils@0.31.18

Runtime dependencies

  • None declared

Peer requirements

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.

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

Evidence and freshness