@netlify/opentelemetry-sdk-setup

Opentelemetry SDK setup script

@netlify/opentelemetry-sdk-setup@4.0.1 was published on 2026-10-21. Its manifest declares 10 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=22.12.0.

All @netlify/opentelemetry-sdk-setup versions · Permanent reference to 4.0.1

Package specifications

Version4.0.1
License declarationMIT
Published2026-10-21T13:20:00.236Z
Node.js requirement>=22.12.0
Type declarationsBundled declarations
Runtime dependency count10
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size17.05 KiB
Published file count12
Package typemodule
ES module entryNot declared
Default entry./lib/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies71
Repository stars260
Repository forks113

Install @netlify/opentelemetry-sdk-setup 4.0.1

npm install @netlify/opentelemetry-sdk-setup@4.0.1
pnpm add @netlify/opentelemetry-sdk-setup@4.0.1
yarn add @netlify/opentelemetry-sdk-setup@4.0.1

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.

Maintained10/10 — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Code-Review10/10 — all changesets reviewed
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
License10/10 — license file detected
Branch-Protection5/10 — branch protection is not maximal on development and all release branches
Security-Policy9/10 — security policy file detected
Binary-Artifacts3/10 — binaries present in source code
Pinned-Dependencies8/10 — dependency not pinned by hash detected -- score normalized to 8
Fuzzing0/10 — project is not fuzzed
SAST5/10 — SAST tool is not run on all commits -- score normalized to 5

Evidence and freshness