@opentelemetry/instrumentation
Base class for node which OpenTelemetry instrumentation modules extend
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@opentelemetry/api-metrics | AI (dependencies): @opentelemetry/api-metrics is a sibling package from the same OpenTelemetry monorepo, published by the same trusted team. This dependency relationship is stable and expected across all versions. | ai | |
| provenance | no-provenance | AI (provenance): This package predates Sigstore provenance adoption on npm. With 63.4M weekly downloads and a long-standing trusted publisher, lack of provenance is not a meaningful risk signal here. | ai | |
| provenance | publisher-changed | AI (provenance): dyladan and pichlermarc are both established OpenTelemetry maintainers; publisher rotation is routine for this org. SLSA provenance confirms CI/CD build. | ai | |
| dependencies | unvetted-dep:@types/shimmer | AI (dependencies): @types/shimmer is a type definition package for shimmer, a legitimate instrumentation utility. Unvetted but low-risk for this established package context. | ai | |
| phantom-deps | phantom-dep:@types/shimmer | AI (phantom-deps): Phantom dependency is expected for framework-scoped type definitions loaded by convention in OpenTelemetry instrumentation. | ai | |
| dependencies | unvetted-dep:@opentelemetry/api-logs | AI (dependencies): @opentelemetry/api-logs is a sibling package from the same official OpenTelemetry JS monorepo, published at matching versions via the same CI/CD pipeline with SLSA provenance. | ai | |
| dependencies | unvetted-peer-dep:@opentelemetry/api | AI (dependencies): @opentelemetry/api is the canonical OpenTelemetry API package; it is a well-known, widely-used package and a standard peer dep for all OpenTelemetry instrumentation packages. | ai |
Versions (showing 51 of 80)
| Version | Deps | Published |
|---|---|---|
| 0.218.0 | 3 / 23 | |
| 0.217.0 | 3 / 23 | |
| 0.216.0 | 3 / 23 | |
| 0.215.0 | 3 / 23 | |
| 0.214.0 | 3 / 23 | |
| 0.213.0 | 3 / 23 | |
| 0.212.0 | 3 / 23 | |
| 0.211.0 | 3 / 23 | |
| 0.210.0 | 3 / 23 | |
| 0.209.0 | 3 / 23 | |
| 0.208.0 | 3 / 24 | |
| 0.207.0 | 3 / 24 | |
| 0.206.0 | 3 / 24 | |
| 0.205.0 | 3 / 25 | |
| 0.204.0 | 3 / 25 | |
| 0.203.0 | 3 / 26 | |
| 0.202.0 | 3 / 26 | |
| 0.201.1 | 5 / 26 | |
| 0.201.0 | 5 / 26 | |
| 0.200.0 | 5 / 27 | |
| 0.57.2 | 6 / 28 | |
| 0.57.1 | 6 / 28 | |
| 0.57.0 | 6 / 28 | |
| 0.56.0 | 6 / 28 | |
| 0.55.0 | 6 / 28 | |
| 0.54.2 | 6 / 28 | |
| 0.54.1 | 6 / 28 | |
| 0.54.0 | 6 / 29 | |
| 0.53.0 | 6 / 29 | |
| 0.52.1 | 6 / 30 | |
| 0.52.0 | 6 / 30 | |
| 0.51.1 | 6 / 30 | |
| 0.51.0 | 6 / 30 | |
| 0.50.0 | 6 / 31 | |
| 0.49.1 | 6 / 31 | |
| 0.49.0 | 5 / 31 | |
| 0.48.0 | 5 / 30 | |
| 0.47.0 | 5 / 29 | |
| 0.46.0 | 5 / 29 | |
| 0.45.1 | 5 / 29 | |
| 0.45.0 | 5 / 29 | |
| 0.44.0 | 5 / 29 | |
| 0.43.0 | 5 / 29 | |
| 0.42.0 | 5 / 29 | |
| 0.41.2 | 5 / 29 | |
| 0.39.1 | 3 / 28 | |
| 0.39.0 | 3 / 28 | |
| 0.38.0 | 3 / 29 | |
| 0.37.0 | 3 / 29 | |
| 0.36.1 | 3 / 29 | |
| 0.36.0 | 3 / 29 |
v0.218.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.217.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.216.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.214.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.213.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.212.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.211.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.210.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.209.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.208.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.207.0
2 findingsThis version was published by a different npm account than previous versions on 2025-10-21. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.206.0
2 findingsThis version was published by a different npm account than previous versions on 2025-10-06. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.205.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.204.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.203.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.202.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.201.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.201.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.200.0
2 findingsThis version was published by a different npm account than previous versions on 2025-03-17. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.57.2
2 findingsThis version was published by a different npm account than previous versions on 2025-02-13. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.57.1
2 findingsThis version was published by a different npm account than previous versions on 2025-01-14. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.57.0
2 findingsThis version was published by a different npm account than previous versions on 2024-12-18. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.56.0
2 findingsThis version was published by a different npm account than previous versions on 2024-12-04. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.55.0
2 findingsThis version was published by a different npm account than previous versions on 2024-11-18. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.54.2
2 findingsThis version was published by a different npm account than previous versions on 2024-11-07. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.54.1
2 findingsThis version was published by a different npm account than previous versions on 2024-11-05. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.54.0
2 findingsThis version was published by a different npm account than previous versions on 2024-10-23. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.53.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.52.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.51.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-09-12. This could indicate a legitimate maintainer transition or an account compromise.
v0.42.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-09-11. This could indicate a legitimate maintainer transition or an account compromise.
v0.41.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-08-08. This could indicate a legitimate maintainer transition or an account compromise.
v0.39.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.