← Home

@opentelemetry/sdk-metrics-base

npm Repository Homepage
9
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

bogdandrutudyladan

Keywords

opentelemetrynodejsmetricsstatsprofiling

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff large-new-source-files AI (source-diff): OpenTelemetry metrics SDK added ESM/ESNext build targets in this major refactor; large file count increase is structural, not injected code. ai
source-diff source-size-tripled AI (source-diff): Size tripling explained by shipping three build targets (CJS, ESM, ESNext) as documented in package.json files/module/esnext fields. ai
phantom-deps phantom-dep:lodash.merge AI (phantom-deps): lodash.merge is a declared runtime dependency; phantom-dep finding is a false positive likely due to indirect import patterns. ai

Versions (showing 9 of 9)

Version Deps Published
0.31.0 4 / 18
0.30.0 4 / 18
0.29.2 4 / 18
0.29.1 4 / 18
0.29.0 4 / 18
0.28.0 4 / 18
0.27.0 4 / 12
0.26.0 4 / 12
0.25.0 4 / 12

v0.31.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.30.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.29.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.29.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.29.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.28.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.27.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.26.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.25.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.