@azure/monitor-opentelemetry 1.14.2

Azure Monitor OpenTelemetry (Node.js)

@azure/monitor-opentelemetry@1.14.2 was published on 2025-11-14. Its manifest declares 28 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=20.0.0.

All @azure/monitor-opentelemetry versions · Permanent reference to 1.14.2 · View npm registry JSON · Latest release

Package specifications

Version1.14.2
License declarationMIT
Published2025-11-14T14:52:38.781Z
Node.js requirement>=20.0.0
Type declarationsBundled declarations
Runtime dependency count28
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size1768.99 KiB
Published file count406
Package typemodule
ES module entry./dist/esm/index.js
Default entry./dist/commonjs/index.js
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies176
Repository stars2301
Repository forks1408

Install @azure/monitor-opentelemetry 1.14.2

npm install @azure/monitor-opentelemetry@1.14.2
pnpm add @azure/monitor-opentelemetry@1.14.2
yarn add @azure/monitor-opentelemetry@1.14.2

Runtime dependencies

Peer requirements

  • None declared

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-Review9/10 — Found 16/17 approved changesets -- score normalized to 9
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
License10/10 — license file detected
Security-Policy10/10 — security policy file detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Branch-Protection5/10 — branch protection is not maximal on development and all release branches
Token-Permissions9/10 — detected GitHub workflow tokens with excessive permissions
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0
Binary-Artifacts9/10 — binaries present in source code
Pinned-Dependencies7/10 — dependency not pinned by hash detected -- score normalized to 7
Fuzzing0/10 — project is not fuzzed

Evidence and freshness