@opentelemetry/propagator-ot-trace
Supply chain provenance
Status for the latest visible version.
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): OpenTelemetry org migrated to GitHub Actions CI/CD publishing; SLSA attestation confirms legitimate CI origin. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy consistent with org-wide CI migration; SLSA provenance attestation confirms legitimate publish. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.29.0 | 0 / 1 | |
| 0.28.3 | 0 / 23 | |
| 0.28.2 | 0 / 23 | |
| 0.28.1 | 0 / 23 |
v0.29.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.28.3
2 findingsThis version was published by a different npm account than previous versions on 2025-09-29. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.28.2
2 findingsThis version was published by a different npm account than previous versions on 2025-09-29. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.28.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.