@opentelemetry/instrumentation 0.201.0
Base class for node which OpenTelemetry instrumentation modules extend
@opentelemetry/instrumentation@0.201.0 was published on 2025-05-15. Its manifest declares 5 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.
All @opentelemetry/instrumentation versions · Permanent reference to 0.201.0 · Latest release
Package specifications
| Version | 0.201.0 |
|---|---|
| License declaration | Apache-2.0 |
| Published | 2025-05-15T18:16:54.859Z |
| Node.js requirement | ^18.19.0 || >=20.6.0 |
| Type declarations | Bundled declarations |
| Runtime dependency count | 5 |
| Peer requirement count | 1 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 591.94 KiB |
| Published file count | 193 |
| Package type | Not declared |
| ES module entry | build/esm/index.js |
| Default entry | build/src/index.js |
| Side effects declaration | false |
| Direct advisories | Unknown |
| Resolved graph dependencies | Unknown |
| Repository stars | 3503 |
| Repository forks | 1185 |
Install @opentelemetry/instrumentation 0.201.0
npm install @opentelemetry/instrumentation@0.201.0 pnpm add @opentelemetry/instrumentation@0.201.0 yarn add @opentelemetry/instrumentation@0.201.0
Runtime dependencies
- shimmer ^1.2.1
- @types/shimmer ^1.2.0
- import-in-the-middle ^1.8.1
- require-in-the-middle ^7.1.1
- @opentelemetry/api-logs 0.201.0
Peer requirements
- @opentelemetry/api ^1.3.0
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.
| Code-Review | 10/10 — all changesets reviewed |
|---|---|
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Maintained | 10/10 — 30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Token-Permissions | 10/10 — GitHub workflow tokens follow principle of least privilege |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| License | 10/10 — license file detected |
| Signed-Releases | 0/10 — Project has not signed or included provenance with any releases. |
| Branch-Protection | 4/10 — branch protection is not maximal on development and all release branches |
| Security-Policy | 10/10 — security policy file detected |
| Pinned-Dependencies | 8/10 — dependency not pinned by hash detected -- score normalized to 8 |
| Fuzzing | 0/10 — project is not fuzzed |
| SAST | 10/10 — SAST tool is run on all commits |
Evidence and freshness
- https://registry.npmjs.org/%40opentelemetry%2Finstrumentation/0.201.0 — retrieved 2026-10-31T21:38:37.005Z
- https://api.deps.dev/v3/projects/github.com%2Fopen-telemetry%2Fopentelemetry-js — retrieved 2026-10-31T21:05:38.387Z