@orpc/otel
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 1.14.12 | 1 / 2 | |
| 1.14.10 | 1 / 2 | |
| 1.14.9 | 1 / 2 | |
| 1.14.8 | 1 / 2 | |
| 1.14.7 | 1 / 2 | |
| 1.14.6 | 1 / 2 | |
| 1.14.5 | 1 / 2 | |
| 1.14.4 | 1 / 2 | |
| 1.14.3 | 1 / 2 | |
| 1.14.2 | 1 / 2 | |
| 1.14.1 | 1 / 2 | |
| 1.14.0 | 1 / 2 | |
| 1.13.6 | 1 / 2 | |
| 1.13.5 | 1 / 2 | |
| 1.13.4 | 1 / 2 | |
| 1.13.3 | 1 / 2 | |
| 1.13.2 | 1 / 2 | |
| 1.13.1 | 1 / 2 | |
| 1.13.0 | 1 / 2 | |
| 1.12.3 | 1 / 2 | |
| 1.12.2 | 1 / 2 | |
| 1.12.1 | 1 / 2 | |
| 1.12.0 | 1 / 2 | |
| 1.11.3 | 1 / 2 | |
| 1.11.2 | 1 / 2 | |
| 1.11.1 | 1 / 2 | |
| 1.11.0 | 1 / 2 | |
| 1.10.4 | 1 / 2 | |
| 1.10.3 | 1 / 2 | |
| 1.10.2 | 1 / 2 | |
| 1.10.1 | 1 / 2 | |
| 1.10.0 | 1 / 2 | |
| 1.9.4 | 1 / 2 | |
| 1.9.3 | 1 / 2 | |
| 1.9.2 | 1 / 2 | |
| 1.9.1 | 1 / 2 | |
| 1.9.0 | 1 / 2 | |
| 1.8.9 | 1 / 2 | |
| 1.8.8 | 1 / 2 | |
| 1.8.7 | 1 / 2 | |
| 1.8.6 | 1 / 2 | |
| 1.8.5 | 1 / 2 | |
| 1.8.4 | 1 / 2 | |
| 1.8.3 | 1 / 2 | |
| 1.8.2 | 1 / 2 | |
| 1.8.1 | 1 / 2 | |
| 1.8.0 | 1 / 2 |
v1.14.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.14.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.14.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.14.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.14.7
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (dinwwwh) on 2026-07-06, 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.
v1.14.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.