@opentelemetry/core 0.6.1
OpenTelemetry Core provides default and no-op implementations of the OpenTelemetry types for trace and metrics
@opentelemetry/core@0.6.1 was published on 2020-04-08. Its manifest declares 3 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=8.0.0.
All @opentelemetry/core versions · Permanent reference to 0.6.1 · Latest release
Package specifications
| Version | 0.6.1 |
|---|---|
| License declaration | Apache-2.0 |
| Published | 2020-04-08T18:37:32.711Z |
| Node.js requirement | >=8.0.0 |
| Type declarations | Bundled declarations |
| Runtime dependency count | 3 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 101.65 KiB |
| Published file count | 63 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | build/src/index.js |
| Side effects declaration | Not declared |
| Direct advisories | Unknown |
| Resolved graph dependencies | Unknown |
| Repository stars | 3503 |
| Repository forks | 1185 |
Install @opentelemetry/core 0.6.1
npm install @opentelemetry/core@0.6.1 pnpm add @opentelemetry/core@0.6.1 yarn add @opentelemetry/core@0.6.1
Runtime dependencies
- semver ^7.1.3
- @opentelemetry/api ^0.6.1
- @opentelemetry/context-base ^0.6.1
Peer requirements
- None declared
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%2Fcore/0.6.1 — retrieved 2026-11-01T07:02:39.108Z
- https://api.deps.dev/v3/projects/github.com%2Fopen-telemetry%2Fopentelemetry-js — retrieved 2026-11-01T03:08:27.797Z