← Home

@opentelemetry/sampler-jaeger-remote

npm Repository Homepage
32
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

dyladanpichlermarcoverbalancenpmjs-accounttrentmmartinkuba

Keywords

opentelemetrynodejsmetricsstats

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): OpenTelemetry JS migrated to GitHub Actions CI publishing; SLSA attestation confirms official pipeline. ai
maintainer-change maintainer-removed AI (maintainer-change): Org-level maintainer rotation in a large OSS project; consistent with GitHub Actions takeover of publishing. ai

Versions (showing 32 of 32)

Version Deps Published
0.221.0 2 / 12
0.220.0 2 / 12
0.219.0 2 / 12
0.218.0 2 / 12
0.217.0 2 / 12
0.216.0 1 / 12
0.215.0 1 / 12
0.214.0 1 / 12
0.213.0 1 / 12
0.212.0 1 / 12
0.211.0 1 / 12
0.210.0 1 / 12
0.209.0 1 / 12
0.208.0 1 / 12
0.207.0 1 / 12
0.206.0 1 / 12
0.205.0 1 / 13
0.204.0 1 / 13
0.203.0 1 / 14
0.202.0 1 / 14
0.201.1 1 / 14
0.201.0 1 / 14
0.200.0 1 / 14
0.57.2 1 / 13
0.57.1 1 / 13
0.57.0 1 / 13
0.56.0 1 / 13
0.55.0 1 / 13
0.54.2 1 / 13
0.54.1 1 / 13
0.54.0 1 / 13
0.53.0 1 / 14

v0.221.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.220.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.200.0

1 finding
INFO Has SLSA provenance attestation provenance

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

1 finding
INFO Has SLSA provenance attestation provenance

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

1 finding
INFO Has SLSA provenance attestation provenance

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

1 finding
INFO Has SLSA provenance attestation provenance

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

1 finding
INFO Has SLSA provenance attestation provenance

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

1 finding
INFO Has SLSA provenance attestation provenance

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

1 finding
INFO Has SLSA provenance attestation provenance

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

1 finding
INFO Has SLSA provenance attestation provenance

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 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.

INFO Publisher changed: pichlermarc → dyladan (on 2024-10-23, now via trusted publisher with provenance) provenance

This version was published by a different npm account (dyladan) than the most recent previously approved version (pichlermarc) on 2024-10-23, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

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