← Home

@opentelemetry/api-metrics

24
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

opentelemetrynodejsbrowserprofilingmetricsstatsmonitoring

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Both obecny and dyladan are known OpenTelemetry JS maintainers; this is a legitimate project-level maintainer transition, not a compromise. ai
phantom-deps phantom-dep:@opentelemetry/api AI (phantom-deps): @opentelemetry/api is a declared runtime dependency in the same org scope; phantom-dep false positive for this package. ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance adoption (published 2021); no-provenance is expected for this era of releases. ai
publish-pattern new-deps-added AI (publish-pattern): @opentelemetry/api is the canonical OpenTelemetry API package; adding it as a dependency is expected for this metrics API package's integration with the main API. ai
maintainer-change maintainer-removed AI (maintainer-change): Normal maintainer rotation in the OpenTelemetry JS project over a long period; publisher dyladan is a long-standing trusted contributor. ai

Versions (showing 24 of 24)

Version Deps Published
1.0.0 1 / 17
0.33.0 1 / 17
0.32.0 1 / 17
0.31.0 1 / 17
0.30.0 1 / 17
0.29.2 1 / 17
0.29.1 1 / 17
0.29.0 1 / 17
0.28.0 1 / 17
0.27.0 0 / 17
0.26.0 0 / 18
0.25.0 0 / 18
0.24.0 0 / 18
0.23.0 0 / 18
0.22.0 0 / 18
0.21.0 0 / 18
0.20.0 0 / 18
0.19.0 0 / 19
0.18.2 1 / 18
0.18.1 1 / 18
0.18.0 1 / 18
0.17.0 1 / 18
0.16.0 1 / 18
0.15.0 1 / 18

v1.0.0

1 finding
INFO No provenance attestation provenance

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

v0.33.0

1 finding
LOW No provenance attestation provenance

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

v0.32.0

1 finding
LOW No provenance attestation provenance

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

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.0

1 finding
LOW No provenance attestation provenance

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

v0.23.0

1 finding
LOW No provenance attestation provenance

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

v0.22.0

1 finding
LOW No provenance attestation provenance

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

v0.21.0

1 finding
LOW No provenance attestation provenance

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

v0.20.0

1 finding
LOW No provenance attestation provenance

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

v0.19.0

1 finding
LOW No provenance attestation provenance

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

v0.18.2

1 finding
LOW No provenance attestation provenance

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

v0.18.1

1 finding
LOW No provenance attestation provenance

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

v0.18.0

1 finding
LOW No provenance attestation provenance

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

v0.17.0

2 findings
HIGH Publisher changed: obecny → dyladan (on 2021-02-17) provenance

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.

LOW No provenance attestation provenance

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

v0.16.0

2 findings
HIGH Publisher changed: dyladan → obecny (on 2021-02-01) provenance

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.

LOW No provenance attestation provenance

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

v0.15.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.