@opentelemetry/winston-transport
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): Transition to GitHub Actions CI/CD publishing for the open-telemetry org; expected and verified by SLSA provenance. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 0.31.0 | 3 / 2 | |
| 0.30.0 | 3 / 2 | |
| 0.29.0 | 2 / 2 | |
| 0.28.0 | 2 / 2 | |
| 0.27.0 | 2 / 2 | |
| 0.26.0 | 2 / 2 | |
| 0.25.0 | 2 / 2 | |
| 0.24.0 | 2 / 2 | |
| 0.23.0 | 2 / 2 | |
| 0.22.0 | 2 / 2 | |
| 0.21.0 | 2 / 2 | |
| 0.20.0 | 2 / 2 | |
| 0.19.0 | 2 / 8 | |
| 0.18.0 | 2 / 8 | |
| 0.17.0 | 2 / 8 | |
| 0.16.2 | 2 / 8 | |
| 0.16.1 | 2 / 8 | |
| 0.16.0 | 2 / 8 | |
| 0.15.0 | 2 / 8 | |
| 0.14.1 | 2 / 8 | |
| 0.14.0 | 2 / 8 | |
| 0.13.0 | 2 / 8 | |
| 0.12.0 | 2 / 8 | |
| 0.11.0 | 2 / 8 | |
| 0.10.1 | 2 / 8 | |
| 0.10.0 | 2 / 8 | |
| 0.9.0 | 2 / 8 | |
| 0.8.0 | 2 / 8 | |
| 0.7.0 | 2 / 8 | |
| 0.6.0 | 2 / 10 | |
| 0.5.0 | 2 / 10 | |
| 0.4.0 | 2 / 10 | |
| 0.3.0 | 2 / 10 | |
| 0.2.0 | 2 / 10 | |
| 0.1.0 | 2 / 10 |
v0.31.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.