@opentelemetry/base
OpenTelemetry base provides base code for the SDK packages
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): mayurkale22 is a long-standing OpenTelemetry contributor (787 approved packages, first seen 2554 days ago); this is a legitimate maintainer transition within the same org. | ai | |
| provenance | no-provenance | AI (provenance): Package was published in 2020 before Sigstore provenance was available on npm; absence of attestation is expected for this era. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 0 / 12 | |
| 0.6.1 | 0 / 12 | |
| 0.6.0 | 0 / 12 | |
| 0.5.2 | 0 / 12 | |
| 0.5.1 | 0 / 12 | |
| 0.5.0 | 0 / 12 | |
| 0.4.0 | 0 / 12 | |
| 0.3.3 | 0 / 12 | |
| 0.3.2 | 0 / 12 | |
| 0.3.1 | 0 / 12 | |
| 0.3.0 | 0 / 12 | |
| 0.2.0 | 0 / 12 | |
| 0.1.1 | 0 / 12 | |
| 0.1.0 | 0 / 12 |
v0.7.0
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.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-02. This could indicate a legitimate maintainer transition or an account compromise.
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 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-03-20. This could indicate a legitimate maintainer transition or an account compromise.
v0.5.0
1 finding[Accepted risk] Package 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.