@opentelemetry/tracing
OpenTelemetry Tracing
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): dyladan is a long-standing OpenTelemetry maintainer (1475 approved packages, 0 rejected). The transition from mayurkale22 occurred in 2020 and is a legitimate project maintainer change within the OpenTelemetry org. | ai | |
| provenance | no-provenance | AI (provenance): Package was published in 2020, before Sigstore provenance attestation was available. Not a meaningful risk signal for this era of publication. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/base | AI (phantom-deps): Same-org transitive/re-exported dependency in OpenTelemetry monorepo; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/core | AI (phantom-deps): Same-org transitive/re-exported dependency in OpenTelemetry monorepo; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/types | AI (phantom-deps): Same-org transitive/re-exported dependency in OpenTelemetry monorepo; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/scope-base | AI (phantom-deps): Same-org transitive/re-exported dependency in OpenTelemetry monorepo; stable pattern for this package. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 0.24.0 | 4 / 22 | |
| 0.23.0 | 4 / 23 | |
| 0.22.0 | 4 / 23 | |
| 0.21.0 | 4 / 23 | |
| 0.20.0 | 4 / 23 | |
| 0.19.0 | 4 / 24 | |
| 0.18.2 | 5 / 23 | |
| 0.18.1 | 5 / 23 | |
| 0.18.0 | 5 / 23 | |
| 0.17.0 | 6 / 23 | |
| 0.16.0 | 6 / 23 | |
| 0.15.0 | 6 / 23 | |
| 0.14.0 | 5 / 22 | |
| 0.13.0 | 5 / 22 | |
| 0.12.0 | 5 / 22 | |
| 0.11.0 | 5 / 22 | |
| 0.10.2 | 4 / 22 | |
| 0.10.1 | 4 / 22 | |
| 0.10.0 | 4 / 22 | |
| 0.9.0 | 4 / 22 | |
| 0.8.3 | 4 / 22 | |
| 0.8.2 | 4 / 22 | |
| 0.8.1 | 4 / 24 | |
| 0.8.0 | 4 / 24 | |
| 0.7.0 | 5 / 24 | |
| 0.6.1 | 5 / 24 | |
| 0.6.0 | 5 / 24 | |
| 0.5.2 | 5 / 24 | |
| 0.5.1 | 5 / 24 | |
| 0.5.0 | 5 / 24 | |
| 0.4.0 | 4 / 24 | |
| 0.3.3 | 4 / 24 | |
| 0.3.2 | 4 / 24 | |
| 0.3.1 | 4 / 24 | |
| 0.3.0 | 4 / 24 | |
| 0.2.0 | 4 / 24 | |
| 0.1.1 | 4 / 20 | |
| 0.1.0 | 4 / 20 |
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
2 findings[Accepted risk] Package 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 2021-02-17. This could indicate a legitimate maintainer transition or an account compromise.
v0.16.0
2 findings[Accepted risk] Package 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 2021-02-01. This could indicate a legitimate maintainer transition or an account compromise.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
2 findings[Accepted risk] Package 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 2020-12-04. This could indicate a legitimate maintainer transition or an account compromise.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
2 findingsThis version was published by a different npm account than previous versions on 2020-09-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
2 findings[Accepted risk] Package 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 2020-07-27. This could indicate a legitimate maintainer transition or an account compromise.
v0.9.0
2 findings[Accepted risk] Package 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 2020-06-18. This could indicate a legitimate maintainer transition or an account compromise.
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
2 findings[Accepted risk] Package 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 2020-05-18. This could indicate a legitimate maintainer transition or an account compromise.
v0.8.0
2 findings[Accepted risk] Package 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 2020-05-12. This could indicate a legitimate maintainer transition or an account compromise.
v0.7.0
2 findings[Accepted risk] Package 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 2020-04-24. This could indicate a legitimate maintainer transition or an account compromise.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
2 findingsThis version was published by a different npm account than previous versions on 2020-04-02. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
2 findingsThis version was published by a different npm account than previous versions on 2020-03-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.