@opentelemetry/instrumentation-redis
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): Legitimate CI/CD migration to GitHub Actions with SLSA provenance for this OpenTelemetry org package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Monorepo sub-package; publish cadence depends on when this specific package changes. | ai | |
| dependencies | unvetted-dep:@opentelemetry/redis-common | AI (dependencies): @opentelemetry/redis-common is an official OpenTelemetry package from the same opentelemetry-js-contrib repository; stable false positive for this package. | ai |
Versions (showing 51 of 73)
| Version | Deps | Published |
|---|---|---|
| 0.69.0 | 3 / 4 | |
| 0.68.0 | 3 / 6 | |
| 0.67.0 | 3 / 6 | |
| 0.66.0 | 3 / 6 | |
| 0.65.0 | 3 / 6 | |
| 0.64.0 | 3 / 6 | |
| 0.63.0 | 3 / 6 | |
| 0.62.0 | 3 / 6 | |
| 0.61.0 | 3 / 6 | |
| 0.60.0 | 3 / 6 | |
| 0.59.0 | 3 / 6 | |
| 0.58.0 | 3 / 6 | |
| 0.57.2 | 3 / 6 | |
| 0.57.1 | 3 / 6 | |
| 0.57.0 | 3 / 13 | |
| 0.56.0 | 3 / 13 | |
| 0.55.0 | 3 / 13 | |
| 0.54.4 | 3 / 13 | |
| 0.54.3 | 3 / 13 | |
| 0.54.1 | 3 / 13 | |
| 0.54.0 | 3 / 13 | |
| 0.53.0 | 3 / 13 | |
| 0.52.0 | 3 / 13 | |
| 0.51.0 | 3 / 13 | |
| 0.50.0 | 3 / 13 | |
| 0.49.1 | 3 / 14 | |
| 0.49.0 | 3 / 14 | |
| 0.48.0 | 3 / 14 | |
| 0.47.0 | 3 / 14 | |
| 0.46.1 | 3 / 14 | |
| 0.46.0 | 3 / 14 | |
| 0.45.0 | 3 / 14 | |
| 0.44.0 | 3 / 14 | |
| 0.43.0 | 3 / 14 | |
| 0.42.0 | 3 / 16 | |
| 0.41.0 | 3 / 16 | |
| 0.40.0 | 3 / 16 | |
| 0.39.1 | 3 / 16 | |
| 0.39.0 | 3 / 16 | |
| 0.38.0 | 3 / 16 | |
| 0.37.0 | 3 / 16 | |
| 0.36.0 | 3 / 16 | |
| 0.35.5 | 3 / 16 | |
| 0.35.4 | 3 / 16 | |
| 0.35.3 | 3 / 16 | |
| 0.35.2 | 3 / 16 | |
| 0.35.1 | 3 / 16 | |
| 0.35.0 | 4 / 16 | |
| 0.34.7 | 3 / 16 | |
| 0.34.6 | 3 / 16 | |
| 0.34.5 | 3 / 17 |
v0.69.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.68.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.47.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.46.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.46.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.45.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.44.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.43.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.42.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.41.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.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
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.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.2
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.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.