Is @opentelemetry/browser-instrumentation safe to use?

@opentelemetry/browser-instrumentation has no known vulnerabilities on the latest version (0.3.0). DepScope rates its health at 60/100 (moderate risk).

What is the latest version of @opentelemetry/browser-instrumentation?

The latest version of @opentelemetry/browser-instrumentation is 0.3.0, released 2026-04-24.

Does @opentelemetry/browser-instrumentation have known vulnerabilities?

No known vulnerabilities on the latest version of @opentelemetry/browser-instrumentation.

Is @opentelemetry/browser-instrumentation deprecated?

No, @opentelemetry/browser-instrumentation is actively maintained. Latest release: 0.3.0 (2026-04-24).

What are alternatives to @opentelemetry/browser-instrumentation?

Popular alternatives to @opentelemetry/browser-instrumentation in npm include: debug, lru-cache, string-width, commander, picomatch.

What license does @opentelemetry/browser-instrumentation use?

@opentelemetry/browser-instrumentation is licensed under Apache-2.0.

@opentelemetry/browser-instrumentation

npmv0.3.0

OpenTelemetry browser instrumentations.

License Apache-2.0permissive3 versions4 maintainers3 deps102 weekly dl

open-telemetry/opentelemetry-browser

/ 100

Health

safe to use

@opentelemetry/[email protected] is safe to use (health: 60/100)

Health breakdown0 – 100

25/25

maintenance

3/20

popularity

25/25

security

3/15

maturity

4/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (3)

@opentelemetry/api-logs @opentelemetry/instrumentation web-vitals

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@opentelemetry/browser-instrumentation