Is @opentelemetry/instrumentation-tedious safe to use?

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

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

The latest version of @opentelemetry/instrumentation-tedious is 0.35.0, released 2026-04-29.

Does @opentelemetry/instrumentation-tedious have known vulnerabilities?

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

Is @opentelemetry/instrumentation-tedious deprecated?

No, @opentelemetry/instrumentation-tedious is actively maintained. Latest release: 0.35.0 (2026-04-29).

What are alternatives to @opentelemetry/instrumentation-tedious?

Popular alternatives to @opentelemetry/instrumentation-tedious in npm include: debug, picomatch, @types/node, source-map, react-is.

What license does @opentelemetry/instrumentation-tedious use?

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

@opentelemetry/instrumentation-tedious

npmv0.35.0

OpenTelemetry instrumentation for `tedious` database client for Microsoft SQL Server

License Apache-2.0permissive50 versions5 maintainers3 deps

open-telemetry/opentelemetry-js-contrib

/ 100

Health

safe to use

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

Health breakdown0 – 100

25/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

5/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Quality signals

OSS Criticality

0.77critical

Health History

Dependency Tree

License Audit

Dependencies (3)

@types/tedious @opentelemetry/instrumentation @opentelemetry/semantic-conventions

API access

Get this data programmatically — free, no authentication.

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