@opentelemetry/redis-common
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.38.3 | 0 / 0 | |
| 0.38.2 | 0 / 4 | |
| 0.38.1 | 0 / 4 | |
| 0.38.0 | 0 / 4 | |
| 0.37.0 | 0 / 4 | |
| 0.36.2 | 0 / 6 | |
| 0.36.1 | 0 / 6 | |
| 0.36.0 | 1 / 6 | |
| 0.35.1 | 0 / 6 | |
| 0.35.0 | 0 / 7 | |
| 0.34.0 | 0 / 7 | |
| 0.33.0 | 0 / 7 |
v0.37.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.36.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.